Skip to main content
Glama
Sign In

Rhylthyme

by com.rhylthyme
OverviewDiscussionsAdmin

Publish timeline image

publish_timeline_image
Destructive

Publish a program's static Gantt image at a public share link and return the image URL, for a client that can't display images in tool results or a person who wants a link to the picture. This puts a public copy of the program online that the person can't remove. Validates first and refuses an invalid program.

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": "<program>"
    },
    "name": "publish_timeline_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
programYesProgram JSON; shape under validate_program.

Output Schema

NameRequiredDescriptionDefault
urlYesPublic URL of the live timeline for the same share.
shareIdYesThe public share's id.
imageUrlYesPublic URL of the PNG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description goes further by explaining that the published copy is public and cannot be removed by the person, and that the tool validates the program and refuses invalid input. That is exactly the irreversibility and failure-mode context an agent needs before a destructive, non-idempotent call.

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 sentences, front-loaded with the action and outcome, followed by the irreversibility warning and validation behavior. Every sentence carries information, though the use-case clause is slightly expansive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is unnecessary, and the description covers purpose, use case, irreversibility, and validation failure. Nothing essential to calling this destructive tool correctly is missing.

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?

Only one parameter and schema coverage is 100%, with the schema itself pointing to validate_program for the program JSON shape. The description adds no further detail about the program payload, so the baseline 3 applies.

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 verb and resource (publish a program's static Gantt image to a public share link) plus the concrete outcome (returns the image URL). This is distinguishable from siblings like preview_timeline and get_renderer_source without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear selection conditions — use when a client cannot display images in tool results, or when a person wants a shareable link to the picture. It stops short of explicitly naming the non-publishing alternative (e.g. preview_timeline) but the conditions are strong enough to route an agent.

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

All Rhylthyme toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources