Skip to main content
Glama

whenship

What if

what_if
Read-onlyIdempotent

Compares a plan before and after a change and reports which finish dates move and which deadlines are newly met or missed. The change is a list of simple changes (move an item to a position, change effort, set or clear a deadline or a can't-start-before date, change a lane's people or availability, add a person or team, add a holiday, change working days, remove an item, change the start date), or an alternative: a whole changed copy of the plan, for anything else (moving work between people, splitting, cutting or adding items, dependencies, hand-offs, several changes at once). Returns the comparison and the changed plan. To apply a change and update the chart in one step, call show_plan with the same changes instead.

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

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
changesNoSimple changes, applied in order
alternativeNoA changed copy of `plan`, in the same format, to compare against it. Items keep their name or id to be matched; `changes`, if also given, apply on top

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 the crucial non-obvious behavior that despite being read-only it returns both the comparison and a changed copy of the plan, and that changes are applied to a copy rather than the stored chart. It does not describe error handling for invalid items or lanes, so it stops short of a 5.

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?

Purpose is front-loaded in the first sentence, followed by input-mode guidance and then the sibling hand-off, so the structure matches reading order for a decision. The parenthetical enumeration of change types is long and dense but each item earns its place by preventing a wrong-mode call; minor penalty for the sentence's length.

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?

This is a complex tool with nested objects and no output schema, so the description must carry the return expectations, and it does at a high level ('the comparison and the changed plan'). The exact shape of the comparison report is left unspecified, which is the main residual gap given there is no output schema to fall back on.

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 description coverage is 100%, so the baseline is 3, but the description goes beyond it by translating the `changes` op union into natural-language categories and by explaining the selection rule between `changes` and `alternative` (and that changes can layer on top of an alternative). That is meaning the schema alone does not convey about when each parameter applies.

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?

The opening sentence states a specific verb and resource ('Compares a plan before and after a change') plus the output dimension ('which finish dates move and which deadlines are newly met or missed'). It also implicitly separates itself from show_plan by framing itself as a comparison rather than an apply-and-update step.

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?

It gives explicit routing between the two input modes: use `changes` for simple mutations (with the operations enumerated) and `alternative` for anything else, listing the 'anything else' cases (moving work between people, splitting, dependencies, hand-offs, several changes at once). It also names the sibling show_plan and the condition that selects it: to apply the change and update the chart in one step.

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.