SiteCheck Jobs & Property

Live position of the International Space Station

realestate_iss_current_location

Read-only

Live position of the International Space Station from wheretheiss.at: latitude, longitude, altitude (km), speed (km/h), and whether it is over daylight. Updates roughly every second on the source; the answer is cached 30 seconds. Not a real-estate dataset. Related tools on this server, for a different need: realestate_nhc_current_storms_v2 when you need active tropical cyclones from the US National Hurricane. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`name`	No
`source`	No
`noradId`	No
`latitude`	No
`checkedAt`	No
`longitude`	No
`altitudeKm`	No
`observedAt`	No
`visibility`	No
`velocityKmh`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that the upstream refreshes about once per second while this tool caches for 30 seconds, so the agent knows the value can lag. It also states the billing model explicitly — $0.002 USDC per successful call via x402 on Base, Solana, or Arc, with failed calls free — which is behavior an agent must know before invoking a paid tool.

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?

It is front-loaded with purpose before caveats and pricing, and each clause carries distinct information: fields, refresh/cache behavior, namespace disambiguation, sibling routing, and cost. It is slightly dense as a single run of clauses — the disambiguation and pricing could be split apart — but nothing is redundant.

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?

For a zero-parameter live-data tool with an output schema already present, the description need not restate return structure, yet it covers the three things an agent cannot infer from schema or annotations: staleness (30s cache), cost and payment rail, and the correct sibling for adjacent needs. Nothing required for correct invocation 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?

There are no input parameters, so there is no parameter semantics to explain and the baseline is 4. The description instead characterizes the payload semantics (units in km and km/h, daylight as a boolean condition), which adds useful interpretive context without pretending to describe inputs.

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 names a concrete resource (International Space Station position) with a source (wheretheiss.at) and enumerates the returned fields: latitude, longitude, altitude, speed, and daylight status. It also explicitly disambiguates against its misassigned namespace with "Not a real-estate dataset," so an agent cannot confuse it with the sibling Zillow/Redfin-style tools.

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?

It provides an explicit alternative and the condition that selects it: use realestate_nhc_current_storms_v2 for active tropical cyclones. What's missing is a 'when not to use' for near-neighbor needs such as historical ISS positions or ground-track predictions, but for a zero-parameter live-reading tool the routing guidance is clear.

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

All SiteCheck Jobs & Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?