Skip to main content
Glama

SeekSat

Satellites up now

whats_up_now
Read-onlyIdempotent

What is in the sky over a location right now, from every satellite in the catalog (about 17,000, active satellites plus CelesTrak's visual group; most debris is not in it). mode "visual" (default) lists sunlit satellites above minElevation while the sky is dark there (Sun more than about 6 degrees down), brightest first; magnitudes are measured for most of the bright satellites (McCants' observations) and estimated for the rest (magnitudeEstimated). mode "radio" lists satellites with known downlinks above minElevation, those with a downlink a hobby receiver can tune (30 MHz to 1 GHz) first, then the more recently heard by SatNOGS stations, then highest first, with their downlinks and reception. Each has azimuth with a compass word, elevation, range, sunlit, magnitude and a url to its page. Satellites whose orbital elements are more than 14 days from now are left out and counted (skippedStaleElements). For upcoming passes rather than this moment, use best_pass or find_passes.

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

Input Schema

NameRequiredDescriptionDefault
latNoobserver latitude in decimal degrees, north positive (-90 to 90). Give it with lon, or give location instead.
lonNoobserver longitude in decimal degrees, east positive and west negative (-180 to 180).
modeNo"visual" (default): sunlit satellites in a dark sky, brightest first; "radio": satellites with known downlinks, highest first, day or night.
limitNohow many satellites to return, 1 to 50. Default 10.
minElevNoold name for minElevation; still accepted.
locationNowhere the observer is, when lat and lon are not given (they win when both are): a Maidenhead grid square (EN52, EN52ve, EN52ve12), coordinates in any common form ("41.88, -87.63", "41.88N 87.63W", "41°52'48"N 87°37'48"W", a Google Maps link or geo: URI), all read locally, or a place name (city, address, landmark) looked up with OpenStreetMap. Prefer lat and lon, or a grid square, when you have them: a place name is a network lookup.
minElevationNolowest elevation to list, in degrees above the horizon (0 to 90). Default 10.
minElevationDegNoold name for minElevation; still accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations: discloses the filtering rule (sunlit above minElevation with Sun >6° below horizon, or known downlinks in radio mode), the staleness cutoff of 14 days with skippedStaleElements counting, and that magnitudes are measured for bright satellites but estimated otherwise (magnitudeEstimated). Annotations already cover read-only/idempotent safety, and this adds the operational behavior that matters.

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 the one-line purpose, then mode behavior, then exclusions, then the sibling alternative — a logical order with no filler. It is a dense paragraph, and splitting the two mode descriptions into separate sentences would improve scanability, but every sentence carries information.

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 return shape itself: azimuth with compass word, elevation, range, sunlit flag, magnitude, and a page url, plus downlinks and reception in radio mode. For an eight-parameter read tool with defaults and multiple accepted location forms, nothing an agent needs to call it correctly is missing.

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%, so baseline is 3, but the description adds meaning the schema does not: the full ordering semantics per mode (brightness vs. tunable-downlink/recency/elevation) and the 14-day element-staleness consequence. It could have noted the lat/lon-vs-location precedence, but that is already documented thoroughly in the schema.

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 ('What is in the sky over a location right now') plus the catalog scope (~17,000 satellites, visual group included, most debris excluded). The closing line explicitly routes upcoming-pass questions to best_pass/find_passes, so an agent can separate this from siblings without opening a 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?

Gives explicit when-not guidance: 'For upcoming passes rather than this moment, use best_pass or find_passes,' and explains when to pick each mode (visual = dark sky, radio = downlinks, day or night). It does not distinguish from get_position or next_visible_pass, but the core selection condition is stated clearly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources