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

orbit-sentinel-mcp

by Viventine-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

get_filing_detail

Read-only

Retrieve full details of a regulatory filing by UUID or agency file number, including spectrum data, orbital parameters, ground stations, signals, related filings, and policy positions.

Instructions

Get full details of a specific regulatory filing, by UUID or agency file number, including spectrum data, orbital parameters, ground stations, signals, related filings, attachments, and (for policy filings) executive summary, overall stance, and structured arguments.

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": {
      "id": "<id>"
    },
    "name": "get_filing_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFiling UUID or agency file number (e.g. SES-STA-20250604-00870, LLO-22-126). A file number shared by several filings returns an error listing their UUIDs. Not a call sign: for a station call sign such as E970199 use search_filings call_sign. Not an SEC accession number (0001415404-26-000042): use search_sec_filings accession_number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • changedInput schema / properties / id / description
      Previous value: -"Filing UUID or agency file number (e.g. SES-STA-20250604-00870, LLO-22-126). A file number shared by several filings returns an error listing their UUIDs"New value: +"Filing UUID or agency file number (e.g. SES-STA-20250604-00870, LLO-22-126). A file number shared by several filings returns an error listing their UUIDs. Not a call sign: for a station call sign such as E970199 use search_filings call_sign. Not an SEC accession number (0001415404-26-000042): use search_sec_filings accession_number"
  2. Changed1 schema field changedv0.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Filing UUID"New value: +"Filing UUID or agency file number (e.g. SES-STA-20250604-00870, LLO-22-126). A file number shared by several filings returns an error listing their UUIDs"
  3. First observedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, so safety is covered. The description adds real value by disclosing the breadth of returned content (spectrum data, orbitals, stations, signals, related filings, attachments, and policy-specific summary/stance/arguments), which the agent cannot otherwise anticipate because there is 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence stating the verb, resource, and identifier types before the payload inventory. It is long but every clause names a distinct content category that has no other documentation channel; nothing is redundant.

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

Completeness4/5

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

With no output schema, the description is the only source of return-content information and it delivers that. Combined with annotations (read-only) and a fully documented single parameter, an agent has enough to invoke it correctly; only minor mechanics like attachment retrieval are unaddressed.

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 coverage is 100% and the single parameter's schema description is already richer than the tool description, covering formats, the ambiguous-file-number error, and routing to search_filings/search_sec_filings. The description merely restates 'UUID or agency file number', so the baseline 3 applies.

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 (Get) and resource (full details of a specific regulatory filing) and enumerates the payload categories, which distinguishes it from the search_* siblings. It does not explicitly name the sibling alternative, but the scope is unambiguous.

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?

Use is implied: call it when you have a filing identifier and need the full record rather than a search result. No explicit when-to-use/when-not or named alternative appears in the description; the routing hints (call sign → search_filings, accession → search_sec_filings) live only in the parameter schema.

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