Skip to main content
Glama
Sign In
Who's in Space

Who's in Space

by andresapitt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ISS live location

iss_location

Get the current latitude and longitude of the International Space Station using live data. No arguments required.

Instructions

Returns the current latitude and longitude of the International Space Station. Live data, no arguments needed.

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_location"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Live data' but does not disclose factors like update frequency, accuracy, or any potential limitations. This is minimal for a tool relying solely on its description.

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 extremely concise with two short sentences, each carrying essential information. It is front-loaded with the purpose and includes only necessary details, making it efficient for an AI agent to parse.

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?

Given the tool's low complexity (zero parameters, simple output), the description is adequate but has gaps: it does not specify the coordinate format (e.g., degrees) or whether the data is cached. The lack of output schema and annotations limits completeness, but the description covers the core functionality.

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 has zero parameters and the schema coverage is 100% (empty properties). The description adds value by explicitly stating 'no arguments needed', confirming that no input is required, which aligns with the baseline score of 4 for zero-parameter tools.

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 the verb 'returns' and the specific resource 'current latitude and longitude of the International Space Station'. This distinguishes it from sibling tools like space_briefing and whos_in_space, which cover different aspects of ISS data.

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 indicates when to use the tool (when you need live ISS location) and explicitly says 'no arguments needed', providing clear usage guidance. However, it does not explicitly state when not to use it or mention alternatives.

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