Skip to main content
Glama

Nasa

by io.github.pipeworx-io

Get Asteroids

get_asteroids
Read-onlyIdempotent

Get near-Earth asteroids approaching within a date range (max 7 days). Returns size, velocity, and miss distance. Example: get_asteroids({ start_date: "2024-01-01", end_date: "2024-01-07", _apiKey: "DEMO_KEY" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyNoNASA API key (optional, defaults to DEMO_KEY)
end_dateYesEnd date in YYYY-MM-DD format (max 7 days after start)
start_dateYesStart date in YYYY-MM-DD format

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asteroidsYesList of near-Earth asteroids (up to 30)
total_countYesTotal count of near-Earth objects in the date range

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that it returns size, velocity, and miss distance, which is consistent and provides extra behavioral context without contradicting annotations.

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?

The description is two sentences plus an example, with no unnecessary words. It is front-loaded with the purpose and constraints, making it highly efficient.

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?

Given the annotations covering safety and idempotency, the output schema, and the description mentioning return fields, the tool definition is fully complete for an AI agent to select and invoke correctly.

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 coverage is 100%, so the description adds value by providing an example call and clarifying the date range constraint. This goes beyond the schema's property descriptions, earning a 4.

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 clearly specifies the verb 'get', the resource 'near-Earth asteroids', and the constraints 'within a date range (max 7 days)'. It also lists key return fields, making it distinct from siblings like get_apod or get_mars_photos.

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?

The description states the maximum date range of 7 days and provides an example, giving clear usage context. However, it does not explicitly mention when not to use this tool or suggest alternatives.

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

All Nasa toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools occupy nearly identical semantic space: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded all route through the same 5,798 tools and differ mainly in output strictness or testing status. The Polymarket cluster also has significant boundary overlap, and the 'Nasa' server name makes the large block of unrelated data tools even more confusing to navigate.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern (get_apod, search_nasa_images, resolve_entity, validate_claim, unsubscribe), and family prefixes like ask_pipeworx and polymarket_ are consistent. A few noun-first outliers like entity_profile, deep_research, and bet_research break the pattern slightly, but the overall style is still readable and predictable.

Tool Count2/5

With 36 tools, this set is well beyond the comfortable 3-15 range and even exceeds the 16-25 'heavy' band. Only about five tools actually relate to the server's apparent NASA identity, while the rest form a general data/Pipeworx utility kit that would be better split into a separate server.

Completeness2/5

For a server named 'Nasa,' the surface is thin: APOD, asteroids, Mars rover photos, solar flares, and image search cover only a slice of NASA's API portfolio, with no launch schedules, Earth imagery, mission/news feeds, or ISS data. The general Pipeworx tools make the server broad but incoherent, and a user focused on NASA would hit dead ends quickly.

Resources