Skip to main content
Glama

Open a recorded run

load_run
Read-onlyIdempotent

Open one recorded run: planned against actual timing per step, what ended each step, pauses. Shows where a plan drifts. Needs the user's Rhylthyme account.

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": {
      "run_id": "<run_id>"
    },
    "name": "load_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoAccess token from the login tool. Omit when the account is connected.
run_idYesRun UUID from list_runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changed
    • changedInput schema / properties / run_id / description
      Previous value: -"The run UUID from list_runs"New value: +"Run UUID from list_runs."
    • changedInput schema / properties / token / description
      Previous value: -"Your Rhylthyme access token from the login tool"New value: +"Access token from the login tool. Omit when the account is connected."
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing auth context (account requirement) and the substance of what is returned — drift between plan and actual, step termination causes, pauses — which the annotations cannot express.

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

Conciseness5/5

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

Three short sentences, front-loaded with the resource and its contents, then the value proposition, then the prerequisite. No padding or restatement of the tool name.

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

Completeness5/5

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

For a simple two-parameter read tool with full schema coverage and rich annotations, the description supplies the one thing structured data lacks: what the returned view contains. No output schema exists, and the description compensates by enumerating the report's contents.

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%, with both token (omit when connected) and run_id (UUID from list_runs) already documented in the schema. The description adds only the account requirement, which overlaps the token parameter's schema text, so the baseline 3 is appropriate.

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?

Specific verb ('Open') plus resource ('one recorded run') and a concrete content inventory: planned vs actual timing per step, what ended each step, and pauses. The phrase 'one recorded run' implicitly separates it from the list-style siblings (list_runs, list_public_runs) and from program-level siblings like load_program.

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 by the framing ('Shows where a plan drifts') and a prerequisite is stated ('Needs the user's Rhylthyme account'), but there is no explicit when-to-use versus analyze_schedule/visualize_schedule/preview_timeline, and no when-not guidance. The run_id prerequisite chain is only conveyed through the schema, not the description.

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.