Skip to main content
Glama

Replay a recorded experiment

replay_experiment
Read-onlyIdempotent

What happened in one recorded real run (e.g. whether a prompt injection leaked data with given defences, or how many answers were made up without a facts sheet): the setup, each step, the result and the model's reply, with a link to run it on the site.

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": {
      "page": "<page>",
      "run": "<run>"
    },
    "name": "replay_experiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
runYesThe run's number from list_experiments
pageYesA 3D page (injection, rag, evals, agent-loop, next-token, embeddings) or a lesson's slug (e.g. prompt-injection, model-routing, hallucination-and-grounding, human-in-the-loop)

Output Schema

NameRequiredDescriptionDefault
textYesThe answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text
linksYesThe AI PM Lab pages the answer links to, where each idea can be tried hands-on

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page / enum
      Previous value: -[
      -  "injection",
      -  "rag",
      -  "evals",
      -  "agent-loop",
      -  "next-token",
      -  "embeddings",
      -  "how-ai-agents-work",
      -  "how-llms-work",
      -  "retrieval-augmented-generation",
      -  "embeddings-and-semantic-search",
      -  "prompt-caching-and-cost",
      -  "multi-agent-systems",
      -  "prompt-injection",
      -  "ai-evals",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "human-in-the-loop",
      -  "hallucination-and-grounding",
      -  "production-monitoring",
      -  "writing-good-prompts",
      -  "reasoning-models",
      -  "model-routing",
      -  "structured-outputs",
      -  "tool-design-and-mcp",
      -  "workflows-vs-agents",
      -  "memory-and-long-conversations",
      -  "reviewing-ai-written-code",
      -  "spec-driven-development",
      -  "letting-agents-edit-tests"
      -]New value: +[
      +  "injection",
      +  "rag",
      +  "evals",
      +  "agent-loop",
      +  "next-token",
      +  "embeddings",
      +  "how-ai-agents-work",
      +  "how-llms-work",
      +  "retrieval-augmented-generation",
      +  "embeddings-and-semantic-search",
      +  "prompt-caching-and-cost",
      +  "multi-agent-systems",
      +  "prompt-injection",
      +  "ai-evals",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "human-in-the-loop",
      +  "hallucination-and-grounding",
      +  "production-monitoring",
      +  "writing-good-prompts",
      +  "reasoning-models",
      +  "model-routing",
      +  "structured-outputs",
      +  "tool-design-and-mcp",
      +  "workflows-vs-agents",
      +  "memory-and-long-conversations",
      +  "reviewing-ai-written-code",
      +  "spec-driven-development",
      +  "letting-agents-edit-tests",
      +  "coding-agent-permissions",
      +  "bug-report-is-the-prompt",
      +  "agent-rules-file"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / page / enum
      Previous value: -[
      -  "injection",
      -  "rag",
      -  "evals",
      -  "agent-loop",
      -  "next-token",
      -  "embeddings",
      -  "how-ai-agents-work",
      -  "how-llms-work",
      -  "retrieval-augmented-generation",
      -  "embeddings-and-semantic-search",
      -  "prompt-caching-and-cost",
      -  "multi-agent-systems",
      -  "prompt-injection",
      -  "ai-evals",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "human-in-the-loop",
      -  "hallucination-and-grounding",
      -  "production-monitoring",
      -  "writing-good-prompts",
      -  "reasoning-models",
      -  "model-routing",
      -  "structured-outputs",
      -  "tool-design-and-mcp",
      -  "workflows-vs-agents",
      -  "memory-and-long-conversations"
      -]New value: +[
      +  "injection",
      +  "rag",
      +  "evals",
      +  "agent-loop",
      +  "next-token",
      +  "embeddings",
      +  "how-ai-agents-work",
      +  "how-llms-work",
      +  "retrieval-augmented-generation",
      +  "embeddings-and-semantic-search",
      +  "prompt-caching-and-cost",
      +  "multi-agent-systems",
      +  "prompt-injection",
      +  "ai-evals",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "human-in-the-loop",
      +  "hallucination-and-grounding",
      +  "production-monitoring",
      +  "writing-good-prompts",
      +  "reasoning-models",
      +  "model-routing",
      +  "structured-outputs",
      +  "tool-design-and-mcp",
      +  "workflows-vs-agents",
      +  "memory-and-long-conversations",
      +  "reviewing-ai-written-code",
      +  "spec-driven-development",
      +  "letting-agents-edit-tests"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / page / enum
      Previous value: -[
      -  "injection",
      -  "rag",
      -  "evals",
      -  "agent-loop",
      -  "next-token",
      -  "embeddings",
      -  "how-ai-agents-work",
      -  "how-llms-work",
      -  "retrieval-augmented-generation",
      -  "embeddings-and-semantic-search",
      -  "prompt-caching-and-cost",
      -  "multi-agent-systems",
      -  "prompt-injection",
      -  "ai-evals",
      -  "prompting-vs-rag-vs-fine-tuning",
      -  "human-in-the-loop",
      -  "hallucination-and-grounding",
      -  "production-monitoring",
      -  "writing-good-prompts",
      -  "reasoning-models",
      -  "model-routing",
      -  "structured-outputs",
      -  "tool-design-and-mcp",
      -  "workflows-vs-agents"
      -]New value: +[
      +  "injection",
      +  "rag",
      +  "evals",
      +  "agent-loop",
      +  "next-token",
      +  "embeddings",
      +  "how-ai-agents-work",
      +  "how-llms-work",
      +  "retrieval-augmented-generation",
      +  "embeddings-and-semantic-search",
      +  "prompt-caching-and-cost",
      +  "multi-agent-systems",
      +  "prompt-injection",
      +  "ai-evals",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "human-in-the-loop",
      +  "hallucination-and-grounding",
      +  "production-monitoring",
      +  "writing-good-prompts",
      +  "reasoning-models",
      +  "model-routing",
      +  "structured-outputs",
      +  "tool-design-and-mcp",
      +  "workflows-vs-agents",
      +  "memory-and-long-conversations"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "links": {
      +      "description": "The AI PM Lab pages the answer links to, where each idea can be tried hands-on",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "description": "The answer in markdown, as shown to the user; for the guides, instructions to follow with the user's text",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text",
      +    "links"
      +  ],
      +  "type": "object"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / page / description
      Previous value: -"injection (prompt injection defences), rag (retrieval), evals (graders), agent-loop, next-token, embeddings"New value: +"A 3D page (injection, rag, evals, agent-loop, next-token, embeddings) or a lesson's slug (e.g. prompt-injection, model-routing, hallucination-and-grounding, human-in-the-loop)"
    • changedInput schema / properties / page / enum
      Previous value: -[
      -  "injection",
      -  "rag",
      -  "evals",
      -  "agent-loop",
      -  "next-token",
      -  "embeddings"
      -]New value: +[
      +  "injection",
      +  "rag",
      +  "evals",
      +  "agent-loop",
      +  "next-token",
      +  "embeddings",
      +  "how-ai-agents-work",
      +  "how-llms-work",
      +  "retrieval-augmented-generation",
      +  "embeddings-and-semantic-search",
      +  "prompt-caching-and-cost",
      +  "multi-agent-systems",
      +  "prompt-injection",
      +  "ai-evals",
      +  "prompting-vs-rag-vs-fine-tuning",
      +  "human-in-the-loop",
      +  "hallucination-and-grounding",
      +  "production-monitoring",
      +  "writing-good-prompts",
      +  "reasoning-models",
      +  "model-routing",
      +  "structured-outputs",
      +  "tool-design-and-mcp",
      +  "workflows-vs-agents"
      +]
  6. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behaviour, so the safety profile is covered. Beyond that the description adds that the output is a single recorded run and includes a link to run it on the site, which is useful context not expressed by annotations; it says nothing about behaviour when the page/run combination is invalid.

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 front-loaded sentence that leads with the resource and follows with illustrative examples. It is slightly convoluted, with a long parenthetical and a dangling 'with a link to run it on the site', but nothing is truly wasted.

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?

An output schema exists, so explaining return contents is partly redundant, and the schema fully documents parameters. What is missing is the operational context, namely that the run number must come from list_experiments and that page and run must correspond, which an agent needs in order to call this without errors.

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?

Schema description coverage is 100%, so both parameters are already documented, including the enumeration of pages and lessons and the run range. The description adds no extra meaning about how page and run interact or what happens on a mismatch, so the baseline 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 states a specific resource and scope: one recorded real run, with its setup, steps, result and model reply. The parenthetical examples (prompt injection with defences, hallucinated answers without a facts sheet) make the content concrete, though it never uses a verb like 'replay' or 'retrieve' and does not explicitly differentiate itself from list_experiments.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The only routing hint, that the run number comes from list_experiments, lives in the schema rather than the description, so an agent must open the schema to learn the prerequisite.

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