preview_smart_mockRender a response body template with its {{faker.*}} placeholders replaced by generated values, using the active project's Smart Mock settings. Use this to check a template before saving it on a rule. Requires project context.
| Name | Required | Description | Default |
|---|---|---|---|
| responseBody | Yes | The response body template containing {{faker.*}} placeholders |
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 readOnlyHint annotation already communicates that the operation is non-destructive, and the description reinforces this by describing rendering and replacement rather than modification. It also adds useful context about using the active project's Smart Mock settings, which helps set expectations without contradicting the annotation.
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 two sentences, front-loads the primary action, and contains no filler or redundant wording. Every sentence adds useful information about purpose, usage, or prerequisites.
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?
The description provides the purpose, usage scenario, and prerequisite ('Requires project context'). It does not describe the output format, but the action of rendering a template makes the expected result reasonably inferable, and no output schema is provided to add further detail.
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 schema fully describes the only parameter, responseBody, and the tool description reinforces its meaning by referring to '{{faker.*}} placeholders' and 'generated values.' Since schema coverage is 100% and the description adds relevant context about how the parameter is interpreted, a slightly above-baseline score is appropriate.
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 clearly states a specific verb ('Render'), the resource ('response body template'), and the behavior ('replace {{faker.*}} placeholders with generated values using the active project's Smart Mock settings'). It is easy to distinguish from sibling tools like test_smart_mock because it focuses on previewing a template before saving.
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 provides explicit usage guidance: 'Use this to check a template before saving it on a rule' and notes the prerequisite 'Requires project context.' It does not explicitly name alternative tools, but the use case is clear enough for an agent to decide when to invoke it.
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.
The tools are mostly distinct with clear descriptions. Some pairs like get_header_policies vs get_resolved_headers or get_environment_verification vs get_monitoring_sync_status could be slightly confusing, but the descriptions clarify scope and purpose.
All tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, update_, manage_, etc.). Even the few bare verbs like 'search' and 'set_context' are consistent with the naming scheme.
With 165 tools, the server is extremely heavy. This far exceeds the 'too many' threshold of 25+, making it difficult for an agent to navigate and select the right tool efficiently.
The tool surface covers a very broad API lifecycle domain: specs, environments, test cases, monitors, mock servers, security, governance, documentation, and team management. Read and write operations are present across most areas, with no obvious missing core functionality.