Rhylthyme MCP Server

List my saved programs

list_my_programs

Read-onlyIdempotent

Retrieve a list of your saved programs from your Rhylthyme account. Use it to review and manage stored schedules and protocols.

Instructions

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

Name	Required	Description	Default
`token`	No	Access token from the login tool. Omit when the account is connected.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the useful context that the user must have a Rhylthyme account, but it does not describe return format, pagination, or failure behavior. No contradiction with annotations.

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 no filler. The core action is front-loaded and the account requirement is stated succinctly. Every word earns its place.

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 read-only list operation with one optional parameter and no output schema, the description is largely sufficient. It could mention what is exactly returned or that only the authenticated user's programs are included, but the title and wording already imply a list of saved programs.

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 input schema fully documents the single token parameter (100% schema description coverage), including guidance to omit it when the account is connected. The description adds no additional parameter meaning, so the baseline of 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?

States a specific action and object: listing the user's saved programs. The possessive 'my' and 'saved programs' clearly separate it from sibling tools like list_runs or list_public_runs, even though it doesn't name them 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?

The description implies usage after the user is connected to their Rhylthyme account, and it is clearly intended for retrieving personal saved programs. However, it does not explicitly mention when to use this instead of alternatives or provide any exclusionary guidance, leaving some routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.