Skip to main content
Glama

Nasa

by io.github.pipeworx-io

Search Nasa Images

search_nasa_images
Read-onlyIdempotent

Search the NASA Image and Video Library for images/videos of any subject — planets, missions, astronauts, launches, galaxies, etc. PREFER for "NASA photos of Jupiter", "images of the Apollo 11 mission", "pictures of a nebula". Returns title, description, date, NASA ID, media type, and a thumbnail URL. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return (default 10, max 50).
queryYesSearch terms, e.g. "jupiter", "apollo 11", "crab nebula".
media_typeNoOptional filter: "image", "video", or "audio".

TDQS

A4.1/5.0
Behavior4/5

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

Adds to annotations by stating return fields (title, description, date, NASA ID, media type, thumbnail URL) and the fact it requires no API key ('Keyless'). Annotations already declare read-only, idempotent, non-destructive behavior. No contradiction.

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?

Two sentences, front-loaded with purpose. Second sentence combines usage hint and return info. Efficient but could be slightly more structured to separate return details.

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 simple search tool with 3 parameters and no output schema, description covers key aspects: scope, usage examples, return fields, and keyless access. Lacks details on pagination or error conditions, but is sufficient for straightforward use.

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 coverage is 100% with clear parameter descriptions. Description adds 'Keyless' but that is about authentication, not parameter meaning. Baseline 3 is appropriate as description does not significantly add to parameter semantics.

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 clearly states it searches the NASA Image and Video Library for images/videos of any subject, with specific examples like planets and missions. The verb 'Search' and resource 'NASA Image and Video Library' are specific. It distinguishes itself from sibling tools by being a specialized image search tool.

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?

Includes 'PREFER for' with concrete query examples, guiding appropriate use. Does not explicitly state when not to use or mention alternatives, but the context is clear given it's a niche tool among diverse siblings.

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.6/5.0
Disambiguation2/5

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), and ask_pipeworx_grounded are three variants of the same router, while bet_research, polymarket_edges, and polymarket_arbitrage all target prediction-market opportunities. The descriptions are detailed, but an agent must read extensively to avoid selecting the wrong tool within each cluster.

Naming Consistency2/5

Naming is a mix of conventions: get_*/search_* for NASA tools, ask_pipeworx_* and polymarket_* family prefixes, plus one-off names like entity_profile, bet_research, deep_research, recent_changes, and scan_dependency. There is no consistent verb_noun or family-wide pattern, making tool selection unpredictable despite each individual name being readable.

Tool Count2/5

36 tools is heavy for a server named Nasa, and only 5 of them are actually NASA-related; the rest form a sprawling general data-research, prediction-market, memory, and subscription toolkit. The count is borderline defensible for a broad data assistant, but it is clearly unjustified under the server's stated NASA identity.

Completeness3/5

As a general data-research assistant the surface is quite complete: discovery, routing, grounded verification, entity profiles, comparisons, memory, subscriptions, and feedback are all covered. As a NASA server, however, there are notable gaps—no EONET events, Earth observation, exoplanet archive, or TLE/mission-specific data—and the large non-NASA tool surface does not fill those gaps.

Resources