Skip to main content
Glama

List my saved programs

list_my_programs
Read-onlyIdempotent

List the user's saved programs. Needs the user's Rhylthyme account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_programs"
  }
}

Input Schema

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

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. Changed1 schema field changed
    • 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 from the login tool"New value: +"Only for apps without account connection: the access token from the login tool. Leave empty when the account is connected."
    • removedInput schema / required
      Removed value: -[
      -  "token"
      -]
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's added value is the authentication requirement, but it does not describe the empty-result case, result size, or pagination behavior.

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 the action front-loaded and no filler. The second sentence is slightly clumsy ('Needs the user's Rhylthyme account') but still carries useful information.

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?

For a zero-required-parameter read tool with complete annotations and full schema coverage, the description is adequate but thin. With no output schema, an agent still gets no sense of what a returned 'program' looks like or whether results are bounded.

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?

The single parameter has 100% schema description coverage, including the note that it comes from the login tool and can be omitted when the account is connected. The description only restates the account requirement, so it adds nothing beyond the schema; 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 verb and resource ('List the user's saved programs'), which is clearly distinct from the data-oriented siblings such as list_runs and list_public_runs. It stops short of explicitly naming those alternatives, so the differentiation is implicit rather than stated.

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?

'Needs the user's Rhylthyme account' gives a real precondition for use, which is more than nothing. However, it never says when to pick this over load_program or the other list tools, and it does not explain what to do when the account is not connected.

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.