Rhylthyme MCP Server

Open a public program

load_public_recipe

Read-onlyIdempotent

Open a public recipe by program UUID to retrieve its summary and live-timeline URL for interactive schedule visualizations.

Instructions

Open a public catalog entry by id: summary plus live-timeline URL.

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_public_recipe"
  }
}

Input Schema

Name	Required	Description	Default
`program_id`	Yes	Program UUID (from search_public_recipes)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new information by stating the return payload ('summary plus live-timeline URL') for a tool with no output schema, though it says nothing about auth or rate limits for public access.

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?

One compact sentence that front-loads the action, the resource, and the selection key, then appends the return value. No filler, no repetition.

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 single-parameter read tool with no output schema, the description covers the essential return content and the annotations cover safety and idempotency. What is missing is any statement of when to prefer this over load_program or list_public_runs.

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% and the single parameter is fully documented there, including its UUID format and provenance. The description only echoes 'by id' and adds nothing the schema does not already say; 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 ('Open') and resource ('a public catalog entry by id') and says what comes back (summary plus live-timeline URL). The 'public' qualifier distinguishes it from load_program, but it never names that sibling explicitly, so the differentiation is inferential 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance; the only routing signal ('from search_public_recipes') lives in the schema's parameter description, not the tool description. An agent must infer that this is the public counterpart to load_program with no help from the text.

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