Skip to main content
Glama
Sign In
satellite-anomaly-mcp

satellite-anomaly-mcp

by Litheshan07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

verify_ground_station_auth

Validates ground station API key and command level to authorize critical satellite safety maneuvers.

Instructions

Verifies Ground Station security context for executing sensitive safety maneuvers.

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": {
      "api_key": "<api_key>",
      "command_level": "<command_level>"
    },
    "name": "verify_ground_station_auth"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyYesGround station authorization key
command_levelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only says 'verifies' without disclosing whether this is a read-only check, what happens on success/failure, or any side effects. The term 'security context' is minimal behavioral context.

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?

One concise sentence with the verb and object front-loaded. No redundant or filler content; every word earns its place.

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?

No output schema and no annotations. The description omits return format, error behavior, and parameter roles, which are critical for a verification tool. The sibling tool list provides external context but the description itself is incomplete for safe invocation.

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?

Schema coverage is 50% (api_key is described, command_level is not). The description adds no parameter-level detail: it doesn't explain how command_level affects verification or which level is required for sensitive maneuvers, leaving the agent to infer from the enum names alone.

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?

Clear verb 'verifies' + specific resource 'Ground Station security context' + scope 'for executing sensitive safety maneuvers'. This distinguishes it from sibling tools like trigger_safe_mode, which actually executes the maneuver, and diagnostic/telemetry tools.

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 phrase 'for executing sensitive safety maneuvers' implies when to use it (before such maneuvers) but there is no explicit guidance on when not to use it or which alternative to choose. No exclusions or sibling comparisons are provided.

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