satellite-anomaly-mcp

evaluate_telemetry

Evaluate satellite telemetry to detect anomalies using safety envelope, space-weather, and sensor isolation checks.

Instructions

Evaluates satellite telemetry frame through safety envelope, space-weather filter, and sensor isolation.

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": {
      "bus_voltage": "<bus_voltage>",
      "battery_temp": "<battery_temp>",
      "tumbling_rate": "<tumbling_rate>",
      "gyro_star_residual": "<gyro_star_residual>",
      "seu_counter": "<seu_counter>",
      "is_saa_crossing": "<is_saa_crossing>"
    },
    "name": "evaluate_telemetry"
  }
}

Input Schema

Name	Required	Description
`bus_voltage`	Yes	Main bus voltage (V)
`seu_counter`	Yes	Single Event Upset counter
`battery_temp`	Yes	Battery temperature (C)
`satellite_id`	No	Satellite ID designation
`tumbling_rate`	Yes	ADCS tumbling rate (deg/s)
`is_saa_crossing`	Yes	Whether satellite is crossing South Atlantic Anomaly
`gyro_star_residual`	Yes	Gyroscope vs Star Tracker residual

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It names the filters used but does not reveal the outcome of the evaluation, whether the tool is read-only, or if it triggers side effects. It is unclear what 'evaluates' means in terms of return values or downstream actions. This is a significant gap for a tool that could lead to isolation or safe mode.

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?

The description is a single, front-loaded sentence that precisely states the action and scope. Every term contributes meaning, with no filler or redundancy. It is an excellent model of conciseness.

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?

Despite a 100% schema coverage, the tool lacks an output schema and has no annotations. The description does not explain what the evaluation returns, how results are encoded, or how this tool relates to sibling actions like trigger_safe_mode or isolate_fault_component. An agent would be uncertain about the tool's role in the broader fault-handling workflow. This incomplete context is a significant limitation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters with units and meanings. The description adds no parameter-specific detail beyond what the schema provides, but it does not need to. Baseline 3 is appropriate since the schema is carrying the semantic load.

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?

The description uses the specific verb 'Evaluates' with a clear resource ('satellite telemetry frame') and three distinctive scoping methods ('safety envelope, space-weather filter, and sensor isolation'). This distinguishes it from siblings like detect_novelty_anomaly or isolate_fault_component, which address different aspects of telemetry handling.

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 usage is implied: one would use this tool to evaluate a telemetry frame. However, there is no explicit 'when to use versus' guidance or mention of alternatives. The description does not state exclusions, but the purpose is clear enough to infer basic usage. It lacks direct comparison to sibling tools.

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

Deploy Server