Skip to main content
Glama

Two Minute Timeline

create_timeline
Read-onlyIdempotent

Generate a slide-deck-quality Gantt timeline: task bars and milestone diamonds laid out across numbered time columns (weeks, sprints, months), with optional labelled section bands that group tasks into phases. Choose it for project plans, roadmaps, launch schedules and anything where WHEN each piece of work happens is the point; use a process diagram instead when only the order of phases matters. Limits: 2–52 columns, up to 100 rows. Set duration 0.25 for a milestone. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unit": "Week",
      "tasks": [
        {
          "name": "Discovery",
          "start": 0,
          "duration": 2
        },
        {
          "name": "Design",
          "start": 1,
          "duration": 2.5
        },
        {
          "name": "Development",
          "start": 3,
          "duration": 3
        },
        {
          "name": "QA & Review",
          "start": 5,
          "duration": 2
        },
        {
          "name": "Launch",
          "start": 7,
          "duration": 0.25
        }
      ],
      "title": "Q3 Product Roadmap",
      "columns": 8
    },
    "name": "create_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoDrawing style, the same in every tool. "regular": clean lines and Inter (the default). "bold": heavier, slightly larger type and thicker lines, for slides read from a distance. "sketch": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.regular
unitNoColumn unit label, e.g. "Week", "Sprint", "Month", "Day", "Q". Headers read "<unit> <number>". Default "Week".Week
startNoNumber of the first column, so 1 gives "Week 1, Week 2…" (default 1).
tasksYesRows in the chart, top to bottom (up to 100). Normally just task bars and milestones, which is all most timelines need. Section bands ({ "type": "section" }) may optionally be inserted to group the tasks below them into labelled phases.
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Project Timeline
widthNoChart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content.
creditNoShows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding).
columnsNoNumber of time columns across the chart (2–52, default 8).
paletteNoHex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray.
labelsInBarsNoDraw each task's name inside its bar (and beside milestone diamonds). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / look
      Added value: +{
      +  "default": "regular",
      +  "description": "Drawing style, the same in every tool. \"regular\": clean lines and Inter (the default). \"bold\": heavier, slightly larger type and thicker lines, for slides read from a distance. \"sketch\": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.",
      +  "enum": [
      +    "regular",
      +    "bold",
      +    "sketch"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the agent knows this is a safe, pure-render call. The description adds real value beyond that: hard limits (2–52 columns, 100 rows), the duration=0.25 milestone convention, the Edit link, and the instruction to always surface the image link because inline images can't be saved. That is useful operational context, though it never covers render cost, latency, or failure modes.

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?

Front-loads purpose, then the alternative, then limits, then output handling. Every sentence carries information, but the paragraph is dense with multiple distinct instruction types crammed together, and the all-caps 'ALWAYS' sentence would read better as a separate closing rule.

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?

For a 10-parameter render tool with no output schema, the description closes the important gaps: it explains what the artifact is, what the limits are, how to handle a milestone, and — critically — what the agent must do with the returned link. An agent can call this correctly with no further information.

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 parameter descriptions are unusually detailed (enum meanings for 'look', palette defaults, labelsInBars, credit). The description's only parameter-adjacent content — the 2–52 column limit, the 100-row cap, and the 0.25 milestone trick — restates facts already present in the schema, so the baseline 3 is correct.

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 ('Generate a slide-deck-quality Gantt timeline') and immediately specifies the visual vocabulary — task bars, milestone diamonds, numbered time columns, section bands. It explicitly contrasts itself with the process diagram sibling, so an agent can route without inspecting other schemas.

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

Usage Guidelines5/5

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

Gives concrete use cases (project plans, roadmaps, launch schedules) and an explicit negative condition: 'use a process diagram instead when only the order of phases matters.' It also tells the agent to infer missing details rather than interrogate the user, which is actionable invocation 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.

Resources