Skip to main content
Glama

faultydata

replay_instructions

How to replay a specimen against a client-under-test (URL, curl, params for seed/key).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesSpecimen ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the shape of the returned guidance (URL, curl command, seed/key parameters), which signals a read-style informational tool, but it never states outright that calling it performs no replay or side effects — an important point given the imperative verb in the name.

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?

A single compact sentence with the core purpose front-loaded and the return contents in a tight parenthetical. No wasted wording, though it is arguably too sparse for a tool with no annotations.

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

Completeness3/5

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

For a one-parameter lookup tool this covers the essentials, and the parenthetical partially substitutes for the absent output schema. However, with no annotations and no output schema, the description should explicitly confirm it only returns instructions rather than triggering a replay, and could point to where specimen IDs come from.

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

Parameters3/5

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

Only one parameter exists and schema description coverage is 100%, with the schema already labeling it 'Specimen ID'. The description adds nothing beyond that (no format hints, no mention of where IDs come from, e.g. list_specimens), so the baseline of 3 applies.

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

Purpose4/5

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

The description identifies a specific resource — replay instructions for a specimen against a client-under-test — and the parenthetical enumerates what the instructions contain (URL, curl, params for seed/key). It reads clearly as a documentation-retrieval tool rather than an execution tool, distinguishing it from siblings like get_specimen and start_battery, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: you call it when you need to replay a specimen manually against a client-under-test. There is no explicit when-to-use versus when-not, no mention of start_battery as the automated alternative, and no prerequisites or exclusions stated.

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