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

kerbal-space-program-mcp

by ziksjksk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ksp_flight_recover

Request recovery or revert of the current flight in Kerbal Space Program when the game permits.

Instructions

Request recovery/revert of the current flight when KSP allows it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.9

TDQS

B3/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden. 'Request' hints the operation may be refused and 'when KSP allows it' hints at a state-dependent precondition, but neither is specified, and nothing is said about whether the flight is terminated, what scene results, or whether the action is reversible.

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?

A single compact sentence with the resource front-loaded and no filler. It is under-specified rather than verbose, but structurally it is efficient.

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?

For a stateful, potentially irreversible game action with no annotations and no output schema, the definition is too thin: it never explains the 'when KSP allows it' precondition, the result of the call, or how it differs from revert/return-to-editor behavior.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The empty schema is consistent with 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?

States a specific verb+resource: recovering/reverting the current flight. However it conflates two distinct operations ('recovery' vs 'revert') and does not distinguish this tool from overlapping siblings like ksp_flight_return_to_editor or ksp_flight_abort.

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?

'When KSP allows it' gestures at a precondition but never says what those conditions are, nor does it name the alternative tools an agent should consider. No explicit when-to-use or when-not-to-use guidance is given.

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