Skip to main content
Glama

apod

Retrieve NASA's Astronomy Picture of the Day for today or a specified date, with automatic fallback to the previous day when the current image is not yet published.

Instructions

今日(または指定日)の NASA の今日の天文写真(APOD)を返す。NASA_API_KEY が必要。

例:「今日の天文写真」「2026-10-01 の APOD」

Args: date: YYYY-MM-DD。省略時は今日(当日分が未公開なら前日へ自動フォールバック)。

回答時はこのリンクをそのまま提示してください。

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

Input Schema

NameRequiredDescriptionDefault
dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.41.4
    • removedInput schema / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / date / default
      Removed value: -null
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • addedInput schema / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"_nasa_apodArguments"
  2. Changed1 schema field changedv0.25.2
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "_nasa_apodOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses two non-obvious behaviors: the NASA_API_KEY requirement and the automatic fallback to the previous day when today's entry isn't published yet. It also instructs the caller to present the returned link as-is. It omits error behavior for out-of-range dates and whether the media may be a video rather than an image.

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?

It is front-loaded with the purpose, then the auth requirement, then examples, then the Args block, then the presentation instruction. Every line earns its place and there is no filler, though the three-part structure is slightly fragmented.

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?

There is no output schema, so the description must explain the return value, and it does at a high level: an APOD with a link that should be shown verbatim, plus auth and fallback behavior. For a one-parameter read tool this is nearly complete; only error and media-type handling are left implicit.

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 0%, so the description has to explain the single parameter, and it does: format YYYY-MM-DD, optional, defaults to today, with the fallback rule spelled out. That is more meaning than the bare schema provides.

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?

The opening sentence states a specific verb and resource: it returns NASA's Astronomy Picture of the Day for today or a chosen date. APOD is a named, unambiguous product, so the purpose is clear even though no sibling is named. It stops short of a 5 because it doesn't explicitly contrast itself with search_space_images or astronomy_news.

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?

It gives concrete trigger examples in Japanese ('今日の天文写真', '2026-10-01 の APOD') that show the agent exactly what a user request looks like. It does not say when NOT to use it or which sibling to prefer, so it is clear context without exclusions.

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