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

kerbal-space-program-mcp

by ziksjksk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ksp_flight_set_sas

Toggle stock SAS on the active vessel via its action group to control stability assist during flight.

Instructions

Enable or disable stock SAS using the active vessel action group.

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": {
      "enabled": "<enabled>"
    },
    "name": "ksp_flight_set_sas"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.9

TDQS

C2.7/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 burden. It indicates a state-changing action (enable/disable) but doesn't disclose whether the change is immediate, whether it requires specific vessel conditions, or what happens if the vessel lacks SAS capability.

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, clear sentence with no wasted words. It front-loads the action and resource, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is too sparse. It omits essential context like scene requirements, potential side effects, and error conditions, leaving an agent under-informed.

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?

With one required parameter and 0% schema description coverage, the description only implies that 'enabled' controls the on/off state. It does not clarify the type, default, or any constraints, adding minimal value beyond the parameter name.

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 and resource: enable/disable stock SAS on the active vessel. It's clearly distinguished from sibling tools like ksp_flight_set_rcs and ksp_flight_set_controls, which handle different control systems.

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?

The description states what the tool does but provides no guidance on when to use it versus alternatives, no prerequisites (e.g., must be in flight scene), and no mention of what happens if the vessel doesn't support SAS.

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