Skip to main content
Glama

Near-earth asteroid approaches (x402)

Near-earth asteroid and comet close approaches in the next days: object, approach time, distance in lunar distances and

near_earth_approaches
Read-onlyIdempotent

Near-earth asteroid and comet close approaches in the next days: object, approach time, distance in lunar distances and km, relative speed, magnitude and a rough size estimate, from NASA/JPL (days=7, max_lunar_distances=20). For space-weather, science, media and curiosity agents; not an impact warning. Pay per call $0.01 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
daysNodays ahead 1-60, default 7
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements
max_lunar_distancesNoonly approaches within this many lunar distances, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the description's added value here is the commercial behavior: $0.01 USDC on Base via x402 and the paired 'not an impact warning' caveat. That payment context is exactly the kind of non-annotation detail worth having, though it stops short of describing cost-per-result variation or failure/refund behavior.

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?

The payload description, audience caveat and pricing fit in two compact sentences with the field list front-loaded. It is dense but every clause carries information; the medium-length field enumeration is the only mild bloat.

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 output schema, the description usefully enumerates the returned fields, and it covers defaults and payment requirements for a 3-parameter, zero-required tool. The gap is that it does not say how results are ordered or capped (e.g., by max_lunar_distances), which matters for interpreting output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters (days, max_lunar_distances, x_payment) are already documented, including ranges and defaults. The description restates the defaults (days=7, max_lunar_distances=20) but adds no new semantics such as filtering behavior or what large lunar-distance values return; baseline 3 applies.

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?

Names the concrete resource (near-earth asteroid and comet close approaches) plus the returned fields (object, approach time, lunar distance/km, relative speed, magnitude, size estimate) and the data source (NASA/JPL). An agent knows exactly what it gets without opening the schema, and no sibling in the catalog overlaps this domain.

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?

Gives audience framing ('space-weather, science, media and curiosity agents') and a negative scope note ('not an impact warning'), which implies when to use it. However it names no alternative tool or fallback for impact-risk questions, so the steering is only partial.

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.

Resources