Skip to main content
Glama

iss_flyover

Read-onlyIdempotent

Get upcoming ISS flyover times for a location using latitude and longitude, optionally specifying the number of flyovers (max 20).

Instructions

Get upcoming ISS flyover times for a location (lat/lon).

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "iss_flyover"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude.
lonYesLongitude.
countNoNumber of flyovers (max 20, default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds no behavioral context of its own — nothing about the time window covered, horizon of 'upcoming', rate limits, or timezone of returned times.

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?

A single tight sentence with the resource and the scoping input front-loaded and no wasted words. It is efficient, though the terseness borders on under-specification rather than polished structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only query with full schema coverage and no output schema, the essentials are present. Still missing is anything about what the returned times look like (array of timestamps? local vs UTC?) or the prediction horizon, which matters for a time-based tool.

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 all three parameters including 'count' (max 20, default 5) are already documented in the schema. The description only echoes lat/lon, adding no format or coordinate-convention detail beyond the structured fields; baseline 3 applies.

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 (get upcoming ISS flyover times) with the scoping qualifier '(lat/lon)', so an agent knows it needs coordinates. It does not, however, distinguish itself from the close sibling iss_pass_times, which plausibly returns the same kind of data.

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?

'Upcoming' implies this is for forward-looking pass prediction rather than current position (iss_location) or crew data (iss_astronauts), but that routing is left implicit. There is no explicit when-to-use statement and no mention of when to prefer iss_pass_times instead.

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

Deploy Server

Other Tools