Skip to main content
Glama

Preview timeline image

preview_timeline
Read-onlyIdempotent

Return a static Gantt image of a program with a caption, for 'show me a preview' or 'a picture of the timeline'. Publishes nothing. Planned versus actual: with run (a run record) it draws the actual bars over the plan.

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

Input Schema

NameRequiredDescriptionDefault
runNoA recorded run of the same program (the `run` object from load_run): draws planned versus actual.
programYesProgram JSON; shape under validate_program.

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. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"Rhylthyme program JSON (same shape visualize_schedule accepts)."New value: +"Program JSON; shape under validate_program."
    • changedInput schema / properties / run / description
      Previous value: -"Optional recorded run of the SAME program (`runs` schema 0.1.0-alpha — the `run` object from load_run). Draws planned-vs-actual: the actual bars over ghost bars at the planned positions, coloured by the sign of each step's end deviation."New value: +"A recorded run of the same program (the `run` object from load_run): draws planned versus actual."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description reinforces them with 'publishes nothing', which is the exact risk an agent might worry about for an image-producing tool. It also explains the behavioral difference when a run is supplied, though it does not describe image format, size, or caption source.

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?

Three short sentences, front-loaded with the return artifact, then the negative scope, then the optional-parameter behavior. No filler and nothing buried.

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 output schema, the description carries the return explanation and does so adequately — a static Gantt image plus caption. For a two-parameter, fully documented, read-only tool this is close to complete; only image format/size expectations are unstated.

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%, so the schema already documents both `program` and `run`, including that `run` draws planned versus actual. The description's 'with `run` (a run record)' adds only light reinforcement rather than new semantics such as where the run object comes from or what happens on program/run mismatch.

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?

Description states a specific verb and resource — returns a static Gantt image of a program — plus the return artifact (image with caption). 'Publishes nothing' explicitly carves it apart from the sibling publish_timeline_image, so an agent can route without opening either 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 concrete user-intent triggers ('show me a preview', 'a picture of the timeline') and an explicit condition for the optional run parameter (planned versus actual). It stops short of naming visualize_schedule as the alternative for interactive/data views, so the routing guidance is clear but not exhaustive.

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.