Skip to main content
Glama
Sign In
space-mcp-server

space-mcp-server

by AiAgentKarl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_asteroid_details

Retrieve detailed information about a near-Earth asteroid using its NEO reference ID, including orbital parameters, close approaches, and physical data.

Instructions

Detaillierte Informationen zu einem bestimmten Asteroiden.

Zeigt Orbitalparameter, alle nahen Vorbeiflüge und physische Daten.

Args: asteroid_id: NEO-Referenz-ID (z.B. "3542519" für Bennu)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asteroid_id": "<asteroid_id>"
    },
    "name": "get_asteroid_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
asteroid_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided; description describes the output but lacks details on rate limits, auth requirements, or side effects. For a read-only tool, it is adequate but not thorough.

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?

Two sentences plus args, front-loaded with purpose. No wasted words. Efficient and clear.

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?

Given the tool's simplicity (1 param, no output schema), description is complete enough. It tells what it does, what it returns, and the parameter meaning. Could mention output format but not critical.

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?

Schema has 0% description coverage, but the description explains the parameter 'asteroid_id' as NEO reference ID with an example, adding meaning beyond the schema.

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?

Description explicitly states 'Detailed information about a specific asteroid' and lists what it shows (orbital parameters, close approaches, physical data). Differentiated from siblings like 'get_near_earth_objects' which lists NEOs.

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?

Implied usage for a single asteroid's details, but no explicit when-to-use or alternatives mentioned. Could be improved by stating not to use for list queries.

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