Skip to main content
Glama

AutoTasker Hub — China Social Data API

iss_position

International Space Station live position: latitude, longitude, altitude, velocity, visibility. $0.01 USDC.

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. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add genuinely useful non-schema context — the six returned fields and a $0.01 USDC cost — which tells the agent this is a metered/paid call and roughly what comes back. It does not state refresh cadence, data freshness/caching, or whether the paid call requires a funded wallet, so the disclosure is partial rather than complete.

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?

A single front-loaded sentence: resource first, then the returned fields, then the price. Nothing is redundant and nothing competes for attention, which is the right size for a trivial zero-argument lookup.

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

Completeness4/5

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

For a zero-parameter, non-destructive read with no output schema and no annotations, the description supplies the essential missing piece — what the response contains — plus cost. Only minor gaps remain: units/format for altitude and velocity (km, km/s?) and update frequency, neither of which would block a correct invocation.

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 no parameter meaning to convey; the baseline for a no-arg tool applies. The description correctly implies the call needs no inputs and instead spends its words on the output shape.

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?

The description names a specific resource (International Space Station position) and enumerates exactly what is returned: latitude, longitude, altitude, velocity, visibility. An agent can tell this is a live ISS telemetry lookup, distinct from the weather, crypto, and search siblings. It stops short of a leading verb (e.g. 'Get the current...'), but the noun phrase is unambiguous.

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?

Usage is only implied: the word 'live' signals real-time current-state data, which is enough for an agent to know it should not be used for historical or forecast queries. There is no explicit when-to-use statement, no exclusion of alternatives, and no note about whether the call should be repeated for tracking.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.