Skip to main content
Glama

Get timeline renderer source

get_renderer_source
Read-onlyIdempotent

Return the open-source timeline renderer's JavaScript (Apache-2.0, about 90 KB, no dependencies) for an HTML page or artifact that cannot load external scripts; it defines Rhylthyme.renderTimeline(container, program).

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": "get_renderer_source"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds genuinely useful context beyond them: license (Apache-2.0), approximate payload size (~90 KB), no external dependencies, and the entry point Rhylthyme.renderTimeline(container, program). It does not say how the source is delivered back (raw text vs. a JSON string field) or whether it can be requested in chunks, which is meaningful for a ~90 KB payload.

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?

A single front-loaded sentence that delivers purpose, use case, size, license, dependency status, and API entry point with no filler. Every clause carries information an agent would otherwise have to guess.

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?

With no parameters and no output schema, the description's job is to explain what comes back and why it is needed, and it does both, including size and API shape. The remaining gap is the concrete return format (how the ~90 KB of JavaScript is surfaced in the response), which matters for handling a large payload but is a minor omission for a zero-argument getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema is trivially complete and the baseline is 4. The description goes slightly beyond the empty schema by documenting the runtime call signature renderTimeline(container, program), clarifying how the returned source is consumed.

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+resource: returns the open-source timeline renderer's JavaScript source. It distinguishes itself from rendering siblings (preview_timeline, visualize_schedule, publish_timeline_image) by being a source fetch rather than a rendering action, and the stated use case ('HTML page or artifact that cannot load external scripts') makes the distinction concrete.

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 a clear condition for use — when the target HTML page or artifact cannot load external scripts — which implies the alternative of just referencing a hosted script elsewhere. It does not explicitly name a sibling tool or state when NOT to use it, so it falls short of full when/when-not/alternatives guidance.

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.