Skip to main content
Glama
Sign In
orbit-sentinel-mcp

orbit-sentinel-mcp

by Viventine-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

research

Read-only

Search space regulatory filings, entities, and spectrum in parallel to answer natural-language questions; filter results by agency (FCC, ITU, UNOOSA) for targeted answers.

Instructions

Primary research tool — searches filings, entities, and semantic index in parallel. Use this FIRST for any question. Pass the agency parameter for agency-specific questions (e.g., agency="FCC" for FCC questions).

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": {
      "question": "<question>"
    },
    "name": "research"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoOptional focus area: filing, entity, spectrum, or general (default: general)
agencyNoFilter all sub-queries by agency (FCC, ITU, UN_OOSA). Recommended for agency-specific questions.
questionYesNatural language question about space regulatory filings, entities, or spectrum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and idempotentHint=false, and the description adds that multiple sources are searched in parallel. However, it does not disclose result merging behavior, limits, or what a non-idempotent follow-up means for the agent, leaving meaningful behavioral gaps for a primary research tool with no output schema.

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?

Three short sentences, front-loaded with the core purpose and routing instruction. Every sentence earns its place, including the brief agency example.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a three-parameter primary tool with no output schema, the description covers purpose, routing, and agency filtering. It omits the focus parameter entirely and does not explain the shape or merging of parallel results, leaving the definition only minimally complete.

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 explains question, focus, and agency. The description reinforces the agency parameter with a usage example but says nothing about the focus parameter, adding only marginal value beyond the schema.

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 states a specific verb and scope: it searches filings, entities, and the semantic index in parallel. Calling itself the 'Primary research tool' and instructing to use it FIRST meaningfully distinguishes it from the many narrower search_* and get_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context ('Use this FIRST for any question') and a specific condition for the agency parameter. It does not name alternatives or describe when not to use it, so it stops short of full when/when-not guidance.

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