Skip to main content
Glama

Nasa Cmr

by io.github.pipeworx-io

Search Granules

search_granules
Read-onlyIdempotent

List the individual data files (granules) of a NASA collection — newest first, with timestamps, file size, and direct download URLs. Filter by time range or bounding box. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25).
concept_idYesCMR collection concept ID, e.g. "C1748058432-LPCLOUD". Get IDs from search_collections.
bounding_boxNoSpatial filter "minLon,minLat,maxLon,maxLat".
temporal_endNoEnd of temporal filter, YYYY-MM-DD.
temporal_startNoStart of temporal filter, YYYY-MM-DD. Granules overlapping the range match.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent. The description adds behavioral traits: newest-first ordering, what fields are returned, and the 'Keyless' claim. No contradictions.

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, front-loaded with primary action and result fields. Every word contributes meaning. No fluff.

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 no output schema, the description still informs about return details (timestamps, file size, URLs). Combined with rich annotations and filter options, it is complete for a list tool.

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% with detailed descriptions. The description adds value by mentioning filter types (time range, bounding box) and guiding users to get collection IDs from search_collections, which compensates for high schema coverage.

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 states the tool lists individual data files (granules) of a NASA collection, newest first, with specific fields like timestamps, file size, and download URLs. It distinguishes from the sibling 'search_collections' tool by specifying granule-level vs collection-level.

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 implies use for granule data filtering by time/bounding box. 'Keyless' hints at no auth barriers. While no explicit 'when not to use' is given, the sibling context (e.g., search_collections) provides clear differentiation.

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

All Nasa Cmr 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.5/5.0
Disambiguation2/5

The tool set mixes NASA-specific tools with a large number of financial and prediction market tools, causing confusion. Within the non-NASA tools, there is significant overlap (e.g., multiple Polymarket analysis tools, several research tools with vague boundaries).

Naming Consistency3/5

Most tools use snake_case, but naming patterns are inconsistent: some start with verbs (search_collections, get_collection), others are noun phrases (entity_profile, deep_research). There is no uniform verb_noun convention across the set.

Tool Count2/5

With 33 tools, the count is high. Although it may be appropriate for the underlying domain (data/prediction markets), it is excessive for the server's stated NASA focus, where only 3 tools are relevant.

Completeness1/5

For a server named 'Nasa Cmr', the tool set is severely incomplete: only three tools cover NASA Earth science (search/granules/collections), lacking any support for missions, datasets, or advanced queries. The non-NASA tools are comprehensive but disconnected from the server name.

Resources