Skip to main content
Glama

whenship

Find options

find_options
Read-onlyIdempotent

Searches realistic changes that would meet more deadlines or make the plan sturdier: reordering, deferring undated work, more availability, one more person, or negotiating a deadline. Every option is re-planned exactly, and returned with its effect and the changes that would apply it (usable with what_if).

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

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
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the read-only, idempotent, non-destructive annotations, it discloses that every candidate is exactly re-planned and that results include both the effect and the changes needed to apply the option. The enumerated search levers further clarify behavior, though details such as option ranking or selection are not explained.

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 dense but readable sentences front-load the purpose, then cover the option space, evaluation behavior, result contents, and workflow integration. The wording earns its place without repeating schema details or annotations.

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 planning tool without an output schema, the description usefully summarizes both the search space and the returned effect-and-changes payload. Together with the rich schema, this is enough to invoke it correctly, though limit semantics and more explicit tool-selection boundaries remain small gaps.

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?

With 67% schema coverage, the schema already explains most of the complex plan structure and the lens values. The description adds domain context about the kinds of plan changes considered, but it does not clarify the top-level inputs directly, particularly the otherwise undocumented limit parameter.

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 description gives a specific verb and resource: it searches plan changes to meet more deadlines or make the plan sturdier. The concrete option categories and the handoff to what_if distinguish this discovery tool from merely evaluating or displaying a plan.

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 clearly establishes when to use the tool: when the user needs ways to improve deadline performance or plan robustness. Mentioning that returned changes are usable with what_if supplies a useful next step, but there is no explicit when-not guidance or direct comparison for choosing between the tools.

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.