Skip to main content
Glama

iss_position

Read-onlyIdempotent

Retrieve the current latitude and longitude of the International Space Station for live tracking or location-based applications.

Instructions

Get the current position of the International Space Station.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety and liveness profile is fully covered structurally. The description adds the word 'current', hinting at a live rather than cached snapshot, but says nothing about update cadence, coordinate format, or data source, which is the kind of context that would actually add value beyond the annotations.

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 front-loaded sentence with no waste. It is arguably too sparse rather than bloated, but as a structural matter it is tight and readable.

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?

With no parameters and no output schema, the description carries the whole burden of explaining what 'position' returns (latitude/longitude, altitude, timestamp?) and how it differs from iss_location. It supplies none of that, leaving an agent to guess at the shape and freshness of the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema imposes no burden. Baseline 4 applies; no parameter-related gaps exist.

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 (Get) plus a precise resource (current position of the ISS), which is clearly a read of live orbital data. However, the sibling set contains iss_location, and the description does nothing to distinguish this tool from that near-duplicate, so an agent cannot tell them apart without opening both schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus iss_location, iss_pass_times, or iss_flyover, nor any stated preconditions (e.g. that it returns a live snapshot rather than a prediction). Usage is only inferable from the name and the phrase 'current position'.

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