Skip to main content
Glama
Sign In
kerbal-space-program-mcp

kerbal-space-program-mcp

by ziksjksk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ksp_flight_clear_maneuver_nodes

Clears all native KSP maneuver nodes during flight after explicit confirmation. Use it to reset your planned trajectory before plotting new burns.

Instructions

Remove all native KSP maneuver nodes after explicit confirmation.

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": {
      "confirm": "<confirm>"
    },
    "name": "ksp_flight_clear_maneuver_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.9

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It discloses that removal happens only after explicit confirmation (a behavioral trait), but does not state whether removal is reversible, what happens to active burns, or what the return value is. Partial disclosure.

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?

Extremely concise single sentence that front-loads the action, resource, and scope. No wasted words.

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 simple destructive action on one boolean parameter with no annotations and no output schema, the description covers the essential action but omits consequences (e.g., what 'native' means, irreversibility, effect on guidance). It's minimally viable but incomplete for a destructive tool.

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?

One required boolean parameter 'confirm' with 0% schema description coverage. The description mentions 'explicit confirmation' which hints at the confirm parameter's purpose, but does not explain what setting confirm=false does or any other semantics. Minimal added meaning.

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 (Remove) and resource (all native KSP maneuver nodes) with clear scope. Distinguished from the sibling ksp_flight_maneuver_nodes (which presumably lists them) and ksp_flight_add_maneuver_node (which adds).

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

Usage Guidelines3/5

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

The phrase 'after explicit confirmation' implies a safety-related usage context, but no explicit when-to-use or when-not-to-use guidance is given, nor are alternatives named. Adequate minimum but with gaps.

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

Deploy Server

Other Tools