Skip to main content
Glama

List recorded runs

list_runs
Read-onlyIdempotent

List recorded runs of a saved program: when, how it ended, actual against planned length. For 'how long did this take last time?'. 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": {
      "program_id": "<program_id>"
    },
    "name": "list_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoAccess token from the login tool. Omit when the account is connected.
program_idYesProgram UUID from list_my_programs.

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 / program_id / description
      Previous value: -"The program UUID from list_my_programs or the program's URL"New value: +"Program UUID from list_my_programs."
    • 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

A3.7/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 useful context beyond that: the account/auth requirement and the shape of the returned data. It stops short of noting pagination or result limits.

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?

Three short sentences, front-loaded with the core action and return fields, with no filler. The trailing account note is slightly abrupt but still earns its place as an auth hint.

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?

For a simple two-parameter read tool with no output schema, the description covers purpose, returned fields, and the auth requirement. Only minor gaps remain (pagination/limits, explicit sibling routing), which are not critical for correct invocation.

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%, so both parameters (token, program_id) are already documented in the schema, including the pointer to list_my_programs. The description adds no parameter-level detail beyond that, 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?

States a specific verb and resource ('List recorded runs of a saved program') and enumerates the returned fields (when, how it ended, actual vs planned length). The 'saved program' scoping implicitly separates it from list_public_runs, but it never names that sibling 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?

Provides a concrete use case ('For how long did this take last time?') that anchors when to reach for it. However, it gives no when-not guidance and does not point to alternatives like list_public_runs or load_run for retrieving a single run.

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.