Skip to main content
Glama

List recorded experiments

list_experiments
Read-onlyIdempotent

The real runs recorded on one of AI PM Lab's 3D pages or lessons, each described by its setup (e.g. which defences or settings were on). Replay one to see what happened.

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>"
    },
    "name": "list_experiments"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that each result carries its setup (e.g. which defences or settings were on), which is genuine beyond-schema context. It says nothing about volume, pagination, ordering, or what happens for a page with zero runs.

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?

Two short sentences with no filler, and the resource scope is placed first. The second sentence is a useful pointer rather than padding. Minor weakness: it describes the objects returned before establishing the listing operation, so the action is slightly back-loaded relative to the title.

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 an output schema present, the description need not explain return shape, and annotations cover the safety profile; the one required parameter is fully documented in the schema. What remains thin is operational context — ordering, result volume, and empty-page behavior — none of which blocks a correct call.

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 coverage is 100% and the single parameter's enum plus description already spell out valid page slugs versus lesson slugs. The description's phrase 'one of AI PM Lab's 3D pages or lessons' merely restates the schema's own distinction. Baseline 3 applies since the schema carries the full parameter burden.

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 names a specific resource — the real recorded runs on a named 3D page or lesson — and the title supplies the 'list' verb. It implicitly separates itself from replay_experiment by describing replay as the follow-up action. It falls just short of 5 because the description itself never states the listing action in a verb-first way.

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 implied rather than stated: an agent can infer it is used to find runs on a given page before choosing one to replay, and 'Replay one to see what happened' gestures at the sibling alternative. There is no explicit when-to-use clause, no statement about pages with no experiments, and no prerequisites.

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