hamgoose

by cooked-ham

Overview Schema Source Related Servers Discussions Admin

Python

Local

mission_plan_view

Fetch the active mission plan to review the structured steps, approval status, and progress toward the goal.

Instructions

The current plan for a mission.

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": {
      "mission_id": "<mission_id>"
    },
    "name": "mission_plan_view"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	No
`mission_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation by saying 'current plan' but does not disclose side effects, freshness, error behavior, or whether it modifies anything.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but this is under-specification rather than effective conciseness. One sentence states only the core purpose and omits necessary contextual information.

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

Completeness2/5

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

With two parameters, no annotations, an output schema, and many sibling tools, the description is incomplete. It does not provide selection criteria, parameter semantics, or behavioral expectations, though the output schema mitigates the need to document return values.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions no parameters. It does not clarify the meaning or usage of mission_id or the optional repo parameter, so an agent cannot determine parameter semantics from the description.

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 identifies the resource ('the current plan for a mission') and the tool name supplies the verb 'view'. It is clear enough to distinguish from related tools like mission_plan and mission_replan, though it does not explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus mission_status, mission_plan, mission_replan, or other siblings. The intended selection context is left entirely to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.