Skip to main content
Glama

cosmik

by com.gocosmik

ISS pass times for a location

get_iss_passes
Read-only

When the International Space Station will pass over a location in the next 3 days: start time (UTC), maximum elevation, duration, and whether the pass is in a good viewing window (evening/pre-dawn). Provide a city name OR latitude+longitude.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in decimal degrees (-90 to 90), used with lon when no city is given
lonNoLongitude in decimal degrees (-180 to 180), used with lat when no city is given
cityNoCity name, e.g. 'Paris', 'New York' — 550+ major cities known; takes precedence over lat/lon

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passesYesUpcoming ISS passes above 10° elevation, soonest first (empty when none in the next 3 days)
locationYesResolved location label, or 'unknown' when the input couldn't be resolved

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already handle read-only and non-destructive hints, and the description adds useful behavioral context: the time range (next 3 days) and the output fields (start time UTC, max elevation, duration, good viewing window). This enriches what the annotations provide without contradicting them.

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 a single, front-loaded sentence that conveys the core purpose, outputs, and input options without redundant words. It is compact and well-structured, earning a top score for conciseness.

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 a complete schema, helpful annotations, and an output schema (per context signals), the description sufficiently covers what the tool does, its inputs, and its outputs. The tool is simple enough that this description, alongside the structured metadata, is complete for an agent to select and invoke 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?

The schema has 100% coverage with detailed descriptions for lat, lon, and city. The description reinforces the 'city OR lat/lon' relationship that is already encoded in the schema, adding minimal new meaning. A baseline of 3 is appropriate given the schema's completeness.

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 clearly states what the tool does: it provides ISS pass times over a location in the next 3 days, including start time, maximum elevation, duration, and viewing-window status. It distinguishes itself from sibling tools (launch news, next launches) by focusing on ISS passes rather than launch events.

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?

The description explicitly instructs users to provide a city name OR latitude+longitude, which clarifies input modes. It does not explicitly mention alternatives or exclusions, but the tool's purpose is specific enough that specifying when to use it is somewhat self-evident, so a 4 is warranted.

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

All cosmik toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a clearly distinct aspect of space activity: ISS passes, launch news, and upcoming launches. There is no overlap in purpose, so an agent can easily select the right tool for a given query.

Naming Consistency5/5

All tool names follow a consistent 'get_' + noun phrase pattern (get_iss_passes, get_launch_news, get_next_launches). This predictable naming convention makes the tool set easy to navigate.

Tool Count5/5

With exactly 3 tools, the server is tightly scoped for its purpose of providing space-related information. Each tool contributes a distinct function, and the count is well below the threshold where cognitive overload becomes a concern.

Completeness4/5

The set covers the primary needs for space enthusiasts: live launch schedules, launch news, and ISS pass predictions. Minor gaps exist (e.g., historical launch data, individual launch details, or satellite tracking), but the core domain is well covered.

Resources