SeekSat

Search satellites

search_satellites

Read-onlyIdempotent

Search the full satellite catalog (about 17,000 objects) by name, alias or NORAD number, best match first. Use it to turn a name like "SDO" or "NOAA 19" into a NORAD number for the other tools; names outside the popular list only resolve directly on an exact whole-name match. To find satellites by downlink kind, search with mode "radio" and the kind as the query (query "sstv").

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": {
      "query": "<query>"
    },
    "name": "search_satellites"
  }
}

Input Schema

Name	Required	Description
`mode`	No	"visual" (default): best name match first; "radio": satellites with known radio downlinks first among equally good matches. To list satellites with a kind of downlink, set mode "radio" and put the kind in query (e.g. query "sstv"); mode itself takes only "visual" or "radio".
`limit`	No	how many results to return, 1 to 20. Default 10.
`query`	Yes	a name, part of one, or a NORAD number, e.g. "sdo", "noaa 19", "25544". With mode "radio", a downlink kind as the whole query (e.g. "sstv", "aprs", "cw") lists satellites that have one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile needs no repetition. The description adds real behavioral context beyond that: catalog scale, best-match-first ranking, the popular-list exact-match limitation, and how mode 'radio' changes ranking. It does not describe what a result record contains beyond implying a NORAD number, which is a modest gap.

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?

Three tightly packed sentences with the core purpose and catalog size front-loaded, followed by the workflow hint and the radio workaround. The radio instruction appears in both the description and the mode schema, a minor redundancy, but the trick is non-obvious enough to justify restating.

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 could say more about what results look like, though it implies name-to-NORAD-number mapping. For a three-parameter lookup tool with full annotation coverage, it supplies the scale, ranking, matching caveat, and mode semantics an agent needs to call it 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 baseline is 3; the schema already documents query, mode, and limit including the radio-kind trick. The description's only genuinely additive parameter insight is the popular-name exact-match caveat for query, since the mode guidance largely restates the enum description.

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?

States a specific verb and resource (search the full satellite catalog, ~17,000 objects) with matching keys (name, alias, NORAD number) and ranking order (best match first). It also defines its role relative to the rest of the toolset: resolving a name into a NORAD number 'for the other tools,' which separates it from pass/position tools without needing to name them.

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 when-to-use guidance (convert a name like 'SDO' or 'NOAA 19' into a NORAD number) plus a valuable caveat that names outside the popular list only resolve on an exact whole-name match. It also explains the non-obvious radio workflow. It stops short of explicit exclusions (e.g., when to prefer identify_satellite), so it is clear context rather than 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.

All SeekSat 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.

Resources

Need Help?