List MockHero's pre-built schema templates for ecommerce, blog, SaaS, and social apps.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description confirms a read-only listing operation, consistent with the readOnlyHint annotation. It adds context that the templates are 'pre-built' and for specific domains, which goes beyond the annotation's basic safety profile. No contradictions; output schema covers return details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, well-structured sentence that front-loads the verb and object, then names the target domains. Every word earns its place with no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only listing tool with an output schema, the description is complete. It tells the agent exactly what is listed and the relevant categories, leaving no ambiguity about purpose or scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema is empty and description need not explain parameter meanings. The baseline score for zero-parameter tools is 4, and no additional parameter info is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'List' with a clear resource ('MockHero's pre-built schema templates') and enumerates the categories (ecommerce, blog, SaaS, social apps). This distinguishes it from sibling tools like list_field_types and generate_from_template.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use the tool: when you need a pre-built schema template for the listed application categories. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to choose it over list_field_types or generate_from_template.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose. generate_test_data and generate_from_template could overlap, but descriptions distinguish custom/plain-English generation from pre-built templates. The payment lifecycle tools (create_agent_checkout, check_agent_checkout_status, claim_agent_api_key) are sequential and clearly scoped.
All tool names follow a consistent snake_case verb_noun pattern (e.g., create_agent_checkout, list_field_types, generate_test_data). generate_from_template uses verb_preposition_noun but remains in the same style. No mixing of conventions.
9 tools is well-scoped for a test data generation service with monetization. Each tool earns its place, covering data generation, schema discovery, and payment flow without redundancy or bloat.
The tool set covers the core generation workflows, schema construction, and the full checkout-to-key-claim lifecycle. Minor gaps exist, such as no API key management (e.g., revoke or refresh) and no template customization, but these are not critical for the primary use case.
