Skip to main content
Glama

Astros

astros
Read-onlyIdempotent

People currently in space, name + craft (ISS / Tiangong / etc.).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astros"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
numberYesNumber of people currently in space
peopleYesList of astronauts/cosmonauts in space
messageYesResponse status message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "description": "Response status message",
      +      "type": "string"
      +    },
      +    "number": {
      +      "description": "Number of people currently in space",
      +      "type": "number"
      +    },
      +    "people": {
      +      "description": "List of astronauts/cosmonauts in space",
      +      "items": {
      +        "properties": {
      +          "craft": {
      +            "description": "Spacecraft name (ISS, Tiangong, etc.)",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Person's name",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "craft"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "message",
      +    "number",
      +    "people"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered elsewhere. The description adds that results reflect who is *currently* in space and that records are keyed by name and craft, but it says nothing about data source, update cadence, or result size, which matters for a live-data lookup.

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 short sentence with the subject and returned fields front-loaded. No filler, no restatement of the title, and the parenthetical examples add information rather than noise.

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?

With no parameters, rich annotations, and an output schema already present, the description only needs to say what the tool returns and it does. The remaining gap is the absence of any indication of data freshness or scope limits, which is a minor omission for a simple read-only lookup.

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 and the schema is an empty object, so there is no parameter meaning to convey. The description correctly implies no inputs are required, matching the baseline for parameterless tools.

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 concrete resource (people currently in space) and the exact fields returned (name + craft, with ISS/Tiangong as examples), which is enough to distinguish it from a positional sibling like iss_now. It stops short of an explicit verb or a direct contrast with that sibling, so it is clear but not maximally differentiating.

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: a zero-parameter tool whose name and description make the use case obvious (current crew roster). There is no explicit when-to-use or when-not-to-use guidance, and the available sibling iss_now is not mentioned, so the agent must infer that astros returns people while iss_now returns the station's position.

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.