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

kerbal-space-program-mcp

by ziksjksk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ksp_flight_clear_control

Release the fly-by-wire control lease and return flight control to Kerbal Space Program or player input.

Instructions

Release the MCP fly-by-wire control lease and return control to KSP/player input.

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_clear_control"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.9

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the key effect (control returns to player/KSP input), which is the important side effect for a lease-release tool. However, it does not say whether releasing a non-held lease errors, whether other flight operations must be stopped first, or the return payload.

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?

A single, front-loaded sentence with the action and outcome stated immediately. No filler or repetition.

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 zero-parameter, no-output-schema teardown tool, the description covers the essential action and its effect. Only edge-case behavior (calling when no lease is held) is left unaddressed.

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 the baseline of 4 applies; there is nothing for the description to disambiguate.

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 ('Release') and a specific resource ('the MCP fly-by-wire control lease'), plus the resulting effect ('return control to KSP/player input'). It is distinguishable from siblings like ksp_flight_set_controls or ksp_flight_abort, though it never explicitly names those alternatives.

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?

Usage is only implied: you call this when you are done with programmatic fly-by-wire control. There is no explicit when-to-use statement, no mention of where the lease is acquired (presumably ksp_flight_set_controls), and no note on how it relates to the guidance or maneuver siblings.

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