Skip to main content
Glama

Nasa Get Apod

nasa_get_apod
Read-onlyIdempotent

Get the NASA Astronomy Picture of the Day with explanation. Optionally specify a date. Example: get_apod({ date: "2024-01-15", _apiKey: "DEMO_KEY" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2024-01-15"
    },
    "name": "nasa_get_apod"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (optional, defaults to today). Range: 1995-06-16 to today.
_apiKeyNoNASA API key (optional, defaults to DEMO_KEY, get a free key at api.nasa.gov)

Output Schema

NameRequiredDescriptionDefault
urlYesURL to the astronomy picture
dateYesDate of the astronomy picture in YYYY-MM-DD format
titleYesTitle of the astronomy picture
hd_urlNoURL to the high-definition version of the picture
copyrightNoCopyright information for the picture
media_typeYesType of media (image or video)
explanationYesExplanation of the astronomy picture

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"NASA API key (optional, defaults to DEMO_KEY — get a free key at api.nasa.gov)"New value: +"NASA API key (optional, defaults to DEMO_KEY, get a free key at api.nasa.gov)"
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered by structured data. The description adds only that results include an explanation, and stays silent on rate limiting and the DEMO_KEY fallback that the schema hints at, which would have been genuinely useful external context.

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 short sentences plus one inline example, with the core action front-loaded and no filler. The example call is compact and directly reflects the schema's own examples.

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?

The tool is simple, has an output schema so return values need not be described, and the input schema fully documents both optional parameters. The remaining gap is minor: no note that results vary by date or that the default DEMO_KEY is rate-limited, but nothing blocks a correct call.

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 the date format, the 1995-06-16 lower bound and the DEMO_KEY fallback are all already documented. The description merely restates that the date is optional and shows an example call, adding no meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and a precisely named resource (NASA Astronomy Picture of the Day) plus 'with explanation', which tells the agent both what it fetches and roughly what comes back. It does not explicitly differentiate from siblings such as search_nasa_images or get_mars_photos, but the named resource is distinctive enough that confusion is unlikely.

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?

'Optionally specify a date' implies the two usage modes (today's picture versus a historical one), so context is implied rather than stated. There is no explicit when-not or pointer to alternative NASA endpooints in the sibling set, leaving the agent to infer the choice.

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.