Skip to main content
Glama

Open a saved program

load_program
Read-onlyIdempotent

Open one of the user's saved programs by id: summary plus live-timeline URL. 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": "load_program"
  }
}

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"New value: +"Program UUID from list_my_programs."
    • changedInput schema / properties / token / description
      Previous value: -"Only for apps without account connection: the access token from the login tool. Leave empty when the account is connected."New value: +"Access token from the login tool. Omit when the account is connected."
  3. Changed2 schema fields changed
    • changedInput schema / properties / token / description
      Previous value: -"Your Rhylthyme access token"New value: +"Only for apps without account connection: the access token from the login tool. Leave empty when the account is connected."
    • changedInput schema / required
      Previous value: -[
      -  "token",
      -  "program_id"
      -]New value: +[
      +  "program_id"
      +]
  4. First observed

TDQS

A3.8/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 genuinely new behavioral context: the tool requires the user's Rhylthyme account and returns a summary plus a live-timeline URL, which tells the agent this has a side effect of yielding a live link rather than a static snapshot.

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?

Two short sentences with zero filler; the identity/scope statement is front-loaded and the auth precondition follows. Every clause carries information an agent can act on.

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?

There is no output schema, and the description compensates by naming the return contents (summary plus live-timeline URL). Combined with the stated auth requirement, an agent has enough to call it correctly; only the distinction from public-program loading tools is left unstated.

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%: the token param explains it comes from the login tool and can be omitted when connected, and program_id explains it comes from list_my_programs. The description only restates 'by id', adding no format or sourcing detail beyond the schema, so 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 ('Open one of the user's saved programs by id') and even previews the payload ('summary plus live-timeline URL'), which separates it from list_my_programs and from load_public_recipe/load_run. It stops short of naming the sibling it differs from, so an agent must infer that 'saved' means private/owned.

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?

Implies the workflow (fetch an id, presumably from list_my_programs, then open it) and states the account prerequisite, but never says explicitly when to use this versus load_public_recipe, load_run, or review_program. Usage is inferable rather than 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.