Clarke GEO registry

clarke_list_slots

List GEO slots in the Clarke registry (curated positions merged with UCS-derived positions). The default is a compact page of 50: slug, label, longitude, region, operatorIdentity (split, single, or none), country, status, and satCount. Pass offset to continue. view=full returns occupancy observations (tleEpoch and tleStale, older than 45 days when a TLE supplied occupancy), operatorMix, FCC rows, disputes, and source vintage, in pages of 10 (max 25). all=true is the explicit full list for that view and is large when view is full. The human Terminal models are not in either view. 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 on the full record). TLE longitude is a tracked position, not an FCC or ITU assignment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clarke_list_slots"
  }
}

Input Schema

Name	Required	Description
`all`	No	Explicit full list for this view
`view`	No	compact (default) or full slot record
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses default page sizes, per-view page caps, the cost of all=true, staleness semantics (tleStale, occupancy older than 45 days), and data-provenance caveats (Terminal models absent, ITU filings not in product, ituRecorded is not_in_product, TLE longitude is a tracked position rather than an assignment). These are exactly the behavioral facts an agent cannot get from the 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?

Front-loaded with purpose, then pagination, then caveats — a sensible order for a scanning agent. It is dense with genuinely useful information, though a few clauses (the SNS shutdown date and ITU Space Explorer pointer) are contextual flavor rather than invocation guidance, and 'all=true is the explicit full list' partly restates the schema.

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 must describe returns and largely does, naming the compact field set and the full-view contents (occupancy observations, operatorMix, FCC rows, disputes, source vintage). It stops short of describing the response envelope or how to detect the end of pagination, which an agent driving offset would want.

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?

Adds real meaning beyond the 50%-covered schema: view=full is described by its contents, all=true is described as the explicit full list, and offset is framed as 'pass offset to continue.' The one gap is that the stated page sizes (50 compact, 10 full, max 25) don't clearly reconcile with limit's schema maximum of 100, leaving limit's semantics ambiguous.

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 and resource (list GEO slots) plus the data provenance (curated positions merged with UCS-derived positions) and the fields returned. It doesn't explicitly name clarke_get_slot as the single-record alternative, leaving the list-vs-get split to inference, but the enumerated field set makes the scope unambiguous.

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?

Gives clear operating guidance: default is a compact page of 50, view=full returns the richer record at pages of 10 (max 25), and all=true is the explicit unpaginated full list that 'is large when view is full.' That tells an agent which parameters to reach for in which situation, though it never names a sibling tool as the alternative.

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.