Skip to main content
Glama
Sign In

SeekSat

by com.seeksat
OverviewDiscussionsAdmin

Popular satellites

list_satellites
Read-onlyIdempotent

List the popular satellites (ISS, Tiangong, Hubble and a few others) with each one's orbit data freshness. This is not the full list: every other tool also accepts any NORAD catalog number, e.g. 25544.

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": "list_satellites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare that this is a read-only, idempotent, non-destructive operation, so the description does not need to restate safety traits. It adds useful behavioral context by disclosing that the result is a curated popular list and that each entry includes orbit data freshness, while also clarifying the limited scope.

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 two tight sentences with no wasted wording. The primary purpose and examples are front-loaded, and the scope caveat follows immediately.

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?

For a zero-parameter read-only list tool with no output schema, the description provides everything an agent needs: what is returned, that orbit data freshness is included, and that the set is intentionally limited. The annotations cover the safety profile, so no behavioral gap remains.

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?

This tool has zero parameters, so the baseline is 4. The description appropriately does not invent parameter details, and its note that other tools accept NORAD catalog numbers further clarifies why this zero-parameter listing tool has no filtering inputs.

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 states a specific verb and resource: list the popular satellites, with named examples (ISS, Tiangong, Hubble) and a clear scope limitation that this is not the full catalog. It also distinguishes the tool's coverage from other tools that accept any NORAD catalog number, so an agent can tell what this tool returns without opening the schema.

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 makes clear this tool is for a curated popular subset and warns that it is not the full list, which implies other tools should be used when a specific NORAD catalog number is needed. The guidance is contextual rather than an explicit when-not-to-use rule or a direct sibling recommendation.

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

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