Clarke GEO registry

clarke_get_slot

Agent slot record for one GEO position by slug (e.g. '19-2e' for 19.2E, '101w' for 101W). Operator identity is operatorMix, with raw source strings on each share. operatorIdentity is split when more than one canonical operator is in the occupancy window, single when one is, none when the window has no attributed operator. Also returns occupancy observations (tleEpoch and tleStale), FCC authorizations, dispute records, ituRecorded, and source vintage (tleEpochMin, tleEpochMax, tleStale, tleStaleAfterDays 45), with provenance on occupancy, UCS, FCC, license, and rights. tleStale is true only for a TLE that supplied occupancy and is older than 45 days. UCS fallback does not invent a TLE epoch. ITU filings are not in this product. ITU Space Explorer is the current ITU source. SNS Online shut down in January 2025 (ituRecorded is not_in_product). TLE longitude is a tracked position, not an FCC or ITU assignment.

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": {
      "slug": "<slug>"
    },
    "name": "clarke_get_slot"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Slot slug, e.g. '19-2e'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- changedInput schema / properties / slug / pattern
```
Previous value: -"^[a-z0-9-]+$"New value: +"^[a-z0-9-]{1,64}$"
```
First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden and does so substantively: it explains operatorIdentity split/single/none semantics, the tleStale 45-day rule, that UCS fallback never invents a TLE epoch, that ITU is out of product scope in favor of ITU Space Explorer, and that TLE longitude is a tracked position rather than an assignment. Gaps remain around error behavior for an unknown slug and any auth or rate-limit constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose is front-loaded in the first sentence, but the body becomes a dense reverse-engineering of the payload with several side facts (SNS Online shutdown date, ITU Space Explorer being current, provenance enumeration). Much of that is valuable given no output schema exists, yet the single-paragraph wall makes it hard to scan.

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 annotations and no output schema, the description correctly front-loads return-value semantics and product-scope caveats, which is exactly what structured fields don't cover here. Only the behavior on an invalid or unknown slug is left unaddressed.

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

Parameters4/5

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

Schema coverage is 100% and the schema already gives an example, but the description adds real meaning by glossing '19-2e' as 19.2E and '101w' as 101W, i.e. the decimal-degrees-plus-hemisphere encoding. That goes beyond the schema's bare 'Slot slug, e.g. 19-2e'.

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?

Opens with a specific verb+resource+scope: 'Agent slot record for one GEO position by slug', and disambiguates the slug encoding with concrete examples. It doesn't distinguish itself from the sibling clarke_list_slots (list vs. single record), but the single-record fetch intent is unmistakable.

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?

Usage is only implied: give a slug, get back the slot record for that GEO position. There is no explicit 'use this when you need one slot; use clarke_list_slots to enumerate' or any stated prerequisite/exclusion, so the agent must infer the boundary with siblings.

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

All Clarke GEO registry tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.