Skip to main content
Glama
Viventine-Space

orbit-sentinel-mcp

by Viventine-Space
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

search_ground_stations

Read-only

Search ground/earth stations by name, band, operator, entity, state, or lat/lon proximity; group results by state or operator and query FCC or national registers.

Instructions

Search ground / earth stations by name, frequency band, operator, entity, U.S. state, or geographic proximity (near='lat,lon' within radius_km, ordered by great-circle distance). Defaults to the FCC IBFS earth-station archive (one row per call sign, through 2025-06-17); source=acma|ised|ofcom reads a national register, source=extracted the stations extracted from filings. Each result is labeled with its source. group_by=state|operator returns call-sign counts per bucket (other sources: group_by=operator, station counts). Use for 'earth stations within 200km of 38.9,-77.0', 'how many V-band earth stations per state', or an operator's gateway footprint.

Input Schema

NameRequiredDescriptionDefault
bandNoSatellite frequency band, one of: L, S, C, X, Ku, Ka, V, E. For fcc and the national registers a station matches only if one of its frequency ranges lies entirely within the band (V = 37,500-51,400 MHz); for source=extracted it is an exact match against the station's extracted band list
nameNoSubstring match on station name / FCC call sign
nearNoProximity anchor as 'lat,lon' (e.g. '38.9,-77.0'); returns stations within radius_km ordered by distance
limitNoMax rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit in about 40 KB and says how many it left out
stateNoU.S. state or territory code of the station site (e.g. AK, HI); requires source=fcc
sourceNoDataset: 'fcc' (default; FCC IBFS earth-station filings through 2025-06-17, one row per call sign, reliable coordinates), 'acma', 'ised' or 'ofcom' (Australian, Canadian or UK earth-station register), or 'extracted' (LLM-extracted from filings, carries band names, coordinates are lossy)
group_byNo'state' or 'operator': return counts per bucket instead of rows. source=fcc counts distinct call signs (total is the call signs matched); source=acma|ised|ofcom|extracted take 'operator' only and count distinct stations
operatorNoSubstring match on operator / licensee name
entity_idNoFilter by resolved operator entity UUID (the filing's applicant); fcc or extracted only
radius_kmNoSearch radius in km for near= (default 500)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.1
    • changedInput schema / properties / group_by / description
      Previous value: -"'state' or 'operator': return distinct call-sign counts per state or operator instead of rows (total is the distinct call signs matched); requires source=fcc"New value: +"'state' or 'operator': return counts per bucket instead of rows. source=fcc counts distinct call signs (total is the call signs matched); source=acma|ised|ofcom|extracted take 'operator' only and count distinct stations"
  2. Changed6 schema fields changedv0.7.0
    • changedInput schema / properties / band / description
      Previous value: -"Frequency band, exact match against the station's band list (e.g. Ku); requires source=extracted"New value: +"Satellite frequency band, one of: L, S, C, X, Ku, Ka, V, E. For fcc and the national registers a station matches only if one of its frequency ranges lies entirely within the band (V = 37,500-51,400 MHz); for source=extracted it is an exact match against the station's extracted band list"
    • changedInput schema / properties / entity_id / description
      Previous value: -"Filter by resolved operator entity UUID; requires source=extracted"New value: +"Filter by resolved operator entity UUID (the filing's applicant); fcc or extracted only"
    • addedInput schema / properties / group_by
      Added value: +{
+  "description": "'state' or 'operator': return distinct call-sign counts per state or operator instead of rows (total is the distinct call signs matched); requires source=fcc",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (default 50, max 500)"New value: +"Max rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit in about 40 KB and says how many it left out"
    • changedInput schema / properties / source / description
      Previous value: -"Dataset: 'fcc' (authoritative FCC IBFS registry, reliable coordinates) or 'extracted' (entity-linked, LLM-extracted from filings, carries bands). Defaults to fcc for proximity, extracted for band/entity searches."New value: +"Dataset: 'fcc' (default; FCC IBFS earth-station filings through 2025-06-17, one row per call sign, reliable coordinates), 'acma', 'ised' or 'ofcom' (Australian, Canadian or UK earth-station register), or 'extracted' (LLM-extracted from filings, carries band names, coordinates are lossy)"
    • addedInput schema / properties / state
      Added value: +{
+  "description": "U.S. state or territory code of the station site (e.g. AK, HI); requires source=fcc",
+  "type": "string"
+}
  3. First observedv0.3.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only annotation, the description discloses the default archive and date coverage, source labeling, source-specific grouping behavior, coordinate reliability for extracted data, and the fact that rows cannot be paged and output is truncated around 40 KB with a count of omitted rows.

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 front-loaded with the core search capability, then layers defaults, grouping behavior, and concrete usage examples. Despite covering a complex 10-parameter tool, every sentence carries useful information and there is no filler.

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

Completeness5/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 supplies the key return-shape context: one row per call sign for FCC data, source-labeled results, group-by count semantics, and truncation behavior for large result sets. It is complete enough for an agent to call and interpret the tool correctly.

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 each parameter thoroughly. The description reinforces cross-cutting behavior such as proximity ordering and group-by counts, but largely restates details already present in the schema rather than adding substantial new parameter semantics.

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 opens with a specific verb-resource pair ('Search ground / earth stations') and enumerates filter dimensions, source datasets, and grouping modes. The earth-station scope and source-specific language make it operationally distinct from satellite- or space-station-oriented 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 examples such as proximity searches, state-level V-band counts, and operator gateway footprints. It does not explicitly state when not to use it or name alternative sibling tools, so it is strong but not fully guided.

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