Skip to main content
Glama

simulate

Read-only

What-if: runs the real planner on a hypothetical change and reports the outcome, without saving anything. Use it to answer 'does X still fit by Friday?', to compare options, or to check consequences before changing anything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
addTasksNo
blockTimesNoTimes that would be unavailable, e.g. a free afternoon or a new meeting
taskChangesNo
maxLoadPercentNo

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 and destructiveHint=false, so the safety profile is covered, and the description adds a genuinely non-obvious trait: it runs the *real* planner, so results are authoritative rather than an approximation. "Without saving anything" reinforces but largely restates readOnlyHint. It says nothing about cost/latency or what the report contains.

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, zero filler, with the what-if framing and the no-persistence guarantee front-loaded before the usage examples. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a fairly complex tool (4 structured change parameters, no output schema), the description covers what it does and when to use it but leaves the shape of the input entirely to an under-documented schema and says only "reports the outcome" about the result. Minimum viable: an agent can choose the tool confidently but must read the schema to call it well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description needs to compensate for the bare parameters, and it does not: addTasks, blockTimes, taskChanges and maxLoadPercent are never mentioned or explained. The description stays purely conceptual ("hypothetical change") and adds no meaning about how to express that change.

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?

"Runs the real planner on a hypothetical change and reports the outcome, without saving anything" states a specific verb (simulate/run planner) and outcome, and the no-save clause implicitly separates it from the mutating replan sibling. An agent can tell this is a dry-run evaluation tool without opening the 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?

It gives three concrete usage situations (does X still fit by Friday, compare options, check consequences before changing anything), which is strong positive guidance. It never names the mutating alternative (e.g., replan) as the choice for when you DO want to commit, so the when-not side is left to inference.

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