Skip to main content
Glama
seoh0711

NASA API Desktop Extension

by seoh0711

get_apod

Retrieve NASA's Astronomy Picture of the Day (APOD) with optional date and HD settings using the NASA API Desktop Extension. Access daily space images easily.

Instructions

NASA의 오늘의 천체 사진(Astronomy Picture of the Day)을 가져옵니다

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD 형식의 날짜 (선택사항, 기본값: 오늘)
hdNo고해상도 이미지 여부 (기본값: false)

Implementation Reference

  • The primary handler function for the 'get_apod' tool. Fetches APOD data from NASA API using provided date and HD parameters, handles errors, and returns formatted markdown text content.
      async getAPOD(args) {
        const { date, hd = false } = args || {};
        const params = new URLSearchParams({
          api_key: this.apiKey,
          hd: hd.toString(),
        });
        
        if (date) {
          params.append('date', date);
        }
    
        const response = await fetch(`${this.baseUrl}/planetary/apod?${params}`);
        const data = await response.json();
    
        if (!response.ok) {
          throw new Error(`NASA API 오류: ${data.error?.message || '알 수 없는 오류'}`);
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `**${data.title}** (${data.date})
    
    ${data.explanation}
    
    ${data.media_type === 'image' ? `이미지 URL: ${data.url}` : `비디오 URL: ${data.url}`}
    
    ${data.copyright ? `저작권: ${data.copyright}` : ''}`,
            },
          ],
        };
      }
  • Input schema definition for the 'get_apod' tool, specifying optional 'date' (string) and 'hd' (boolean) parameters.
    inputSchema: {
      type: 'object',
      properties: {
        date: {
          type: 'string',
          description: 'YYYY-MM-DD 형식의 날짜 (선택사항, 기본값: 오늘)',
        },
        hd: {
          type: 'boolean',
          description: '고해상도 이미지 여부 (기본값: false)',
          default: false,
        },
      },
    },
  • server/index.js:37-54 (registration)
    Tool registration in the listTools handler, defining name, description, and input schema for 'get_apod'.
    {
      name: 'get_apod',
      description: 'NASA의 오늘의 천체 사진(Astronomy Picture of the Day)을 가져옵니다',
      inputSchema: {
        type: 'object',
        properties: {
          date: {
            type: 'string',
            description: 'YYYY-MM-DD 형식의 날짜 (선택사항, 기본값: 오늘)',
          },
          hd: {
            type: 'boolean',
            description: '고해상도 이미지 여부 (기본값: false)',
            default: false,
          },
        },
      },
    },
  • Dispatch registration in the callTool request handler, routing 'get_apod' calls to the getAPOD method.
    case 'get_apod':
      return await this.getAPOD(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool fetches data, implying a read-only operation, but does not disclose any behavioral traits such as rate limits, authentication needs, error handling, or response format. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to quickly understand the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavioral aspects and usage context. Without an output schema, it does not explain return values, which is a minor gap but acceptable given the simplicity.

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?

The input schema has 100% description coverage, fully documenting both parameters ('date' and 'hd') with their types, defaults, and formats. The description does not add any additional meaning beyond what the schema provides, such as explaining parameter interactions or constraints. Given the high schema coverage, a baseline score of 3 is appropriate.

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 description clearly states the tool's purpose: 'NASA의 오늘의 천체 사진(Astronomy Picture of the Day)을 가져옵니다' translates to 'Fetches NASA's Astronomy Picture of the Day for today.' It specifies the verb ('가져옵니다' - fetches) and resource (NASA's APOD), but does not explicitly distinguish it from sibling tools like 'get_earth_imagery' or 'search_nasa_images,' which reduces it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions, such as comparing it to sibling tools like 'get_mars_rover_photos' or 'search_nasa_images.' This lack of usage instructions leaves the agent without clear direction.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/seoh0711/dxt_nasa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server