Skip to main content
Glama

whenship

Export plan

export_plan
Read-onlyIdempotent

Returns the plan as a file: json (the whenship save file, re-openable on the website and in Claude), csv (one row per item with dates), ics (calendar with finish dates and deadlines), markdown (the report), or link (a share link with the whole plan inside it). Spreadsheet (XLSX) and image exports are in the chart’s Export menu.

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>",
      "format": "<format>"
    },
    "name": "export_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
formatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, closed-world and non-destructive, so the safety profile is covered without the description. What the description adds is substantive output disclosure — the JSON is a re-openable save file, the CSV is one row per item with dates, the ICS carries finish dates and deadlines — which matters because there is no output schema. It does not say whether the `link` format mints a persistent shareable URL, a side effect worth flagging on a read-only tool.

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?

Two sentences, front-loaded with the core action and the format enumeration, then a disposal rule for the formats it does not handle. No filler or repetition.

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 read-only export with no output schema and a deeply nested plan object, the description covers the one thing the agent cannot infer — what each returned artifact contains. The heavy nested plan/lanes structure is thoroughly documented in the schema itself, so little is left missing beyond link persistence behavior.

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 67%, and the description compensates by explaining what each `format` enum value actually yields, which the bare enum names ("csv", "ics") do not convey. The `lens` and `plan` parameters are left to the schema, which documents them well, including the instruction to pass the plan unchanged.

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 ("Returns the plan as a file") and immediately enumerates the five concrete output formats, so an agent knows exactly what the tool produces. It is unmistakably distinct from the sibling read/analysis tools show_plan, find_options and what_if without needing to open 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?

The format list doubles as guidance on which output to pick for a given user request, and the closing sentence explicitly redirects XLSX and image exports to the chart's Export menu, i.e. a clear when-not case. It stops short of stating when to call this versus show_plan for simply viewing the plan, so it is clear but not fully routing.

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.