Skip to main content
Glama

whenship

Show plan

show_plan
Read-onlyIdempotent

Schedules work for a small team and shows an interactive Gantt chart: finish dates per item, deadline risk (on time / tight / late, with a rough chance), what sets the end date, and the best options to meet more deadlines. Use for "when will this ship", "can we make these deadlines", prioritising several projects or clients, and capacity planning. Input: people or teams (lanes) and items in priority order with effort in working days. Returns a text summary plus the chart, which the user edits directly. changes apply edits first (the answer compares before and after); suggestions are options of your own (title + changes), each measured exactly and shown in the chart for the user to apply.

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": {
      "plan": "<plan>"
    },
    "name": "show_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
lensNoWhich dates to show: planned = as estimated (default), likely 1.6×, safe bet 3.1×
planYesA whenship plan. Pass the current plan (from the chart or the last tool result) unchanged unless the user asked for changes
changesNoEdits to apply first, in order (same format as what_if)
suggestionsNoUp to three options you propose, after checking them with what_if

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds non-obvious behaviour on top: the result is a text summary plus an interactive chart the user edits directly, edits are applied first and the answer compares before and after, and suggestions are 'measured exactly' and rendered into the chart for the user to apply. Nothing contradicts the read-only annotation, since `changes` are applied to a hypothetical copy for comparison rather than persisted.

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-loaded with what it does and what it returns, then use cases, then input shape, then the meaning of the two optional parameters — a sensible order for a complex tool. Roughly 120 words for a four-parameter nested schema is economical. The closing sentence is dense, packing changes, before/after comparison and suggestions into one clause, which slightly hurts scanability.

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 complex nested-plan tool with no output schema, the description carries the return-value burden well: it states the response is a text summary plus a chart and enumerates what the chart shows. It also states the plan-pass-through convention that prevents accidental loss of the current plan. Gaps remain around the `lens` date-multiplier parameter, error or infeasible-plan behaviour, and the instruction to pre-check suggestions with what_if, which appears only in the schema.

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?

Schema coverage is 100%, so the baseline is 3 and the schema already documents lanes, items, work entries and the change-op union. The description still adds meaning the schema does not: items are consumed in priority order with effort in working days, and it clarifies the three-way relationship between `plan` (pass unchanged unless the user asked for changes), `changes` (applied first, answer compares before and after) and `suggestions` (up to three of the agent's own options, measured exactly and shown for the user to apply). The `lens` parameter is never mentioned, keeping it below 5.

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 names a specific verb and resource ('Schedules work for a small team and shows an interactive Gantt chart') and enumerates the concrete outputs: finish dates per item, deadline risk buckets with rough probability, the end-date driver, and mitigation options. That is far more specific than the name or title alone. It stops short of a 5 because it never explicitly contrasts itself with the siblings it overlaps with most (find_options, what_if), so an agent must infer the boundary from a passing schema mention of what_if.

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?

Concrete trigger phrases are given ('when will this ship', 'can we make these deadlines', prioritising several projects or clients, capacity planning), which is strong positive routing. It also disambiguates the two editing inputs: `changes` are real edits applied first with a before/after comparison, while `suggestions` are the agent's own options for the user to apply. No explicit when-not-to-use case or named alternative is offered, so it is not a 5.

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.