Skip to main content
Glama

get_simulator_spec

Retrieve the complete reference specification for the Simceptor simulator, including: all dynamic expression placeholders (request extractors, random/UUID/date generators, multi-locale faker keys, environment/state variables, '__repeat' array loops, and Handlebars helpers), all rule condition field prefixes and comparison operators, Rule Engine evaluation order, stateful session simulation guide, outbound webhook capabilities, Local Webhook Relay setup, and standard response headers. ALWAYS call this tool first when setting up mocks for a new task to understand all supported syntax and features.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_simulator_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties
      Added value: +{}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. "Retrieve" implies a read-only lookup and the enumerated contents give a good sense of what comes back, but it never states the return format (prose vs. structured), its likely large size, or that no server state is modified. Adequate but incomplete for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource, then the detail list, then the usage directive — a sensible order. The parenthetical enumeration is dense but each item names a distinct capability area the agent will need, so little is wasted; only minor tightening is possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description must substitute for the return-value documentation, and it does so by enumerating the spec's sections. The remaining gap is the shape and size of the response, which matters for a reference document that may be large.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema-completeness baseline of 4 applies. The description correctly introduces no parameter concepts, avoiding confusion about arguments that do not exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ("Retrieve") with a named resource ("complete reference specification for the Simceptor simulator") and enumerates the concrete sections it contains (placeholders, operators, evaluation order, webhooks, relay setup, headers). No sibling tool in the list provides the spec, so it is unambiguous against the surrounding mock/rule management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear, imperative call condition: "ALWAYS call this tool first when setting up mocks for a new task." It does not state when not to call it (e.g., updating an existing mock or debugging simply by using the spec it already has), so it lacks exclusions, but the primary trigger is explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources