satellite-anomaly-mcp

isolate_fault_component

Isolate suspect satellite components or switch to redundant subsystems to contain faults and maintain operational integrity.

Instructions

Issues command to isolate suspect satellite component or switch to redundant subsystem.

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": {
      "component": "<component>",
      "action": "<action>"
    },
    "name": "isolate_fault_component"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`component`	Yes
`satellite_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that a command is issued but does not describe side effects, reversibility, authorization needs, or consequences of the isolate/switch actions. This is insufficient for a mutating command tool.

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?

The description is a single, efficiently worded sentence with no filler. It is appropriately front-loaded and avoids redundancy, though it is so brief that it omits critical details. The conciseness itself is good, but substance is minimal.

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 tool with 3 parameters, no annotations, and no output schema, the description is severely incomplete. It misses when to use the tool, operational constraints, expected outcomes, and any safety or prerequisite information, making it inadequate for reliable autonomous use.

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 does not explain any parameter. It does not define the enum values for 'action' and 'component', nor does it clarify the optional 'satellite_id'. The agent lacks essential meaning for correct invocation.

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 uses a specific action ('issues command') and clearly specifies the resource (suspect satellite component) with two alternative actions: isolate or switch to redundant subsystem. This distinguishes it from sibling tools that are analytic or safety-mode focused, although 'isolate' could be more precisely defined.

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?

No guidance is provided on when to use this tool versus alternatives like trigger_safe_mode or evaluate_telemetry. There are no conditions, prerequisites, or exclusions mentioned, leaving the agent without context for appropriate selection.

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

Deploy Server