Skip to main content
Glama

search_space_images

Search NASA's Image and Video Library for space images—planets, satellites, missions—and display them directly in chat.

Instructions

惑星・人工衛星・宇宙ミッションの画像を NASA Image & Video Library から検索し表示する。

LLM向けに structuredContent へJSON(title/date/nasa_id/image_url など)を返し、
content にはチャット表示用のサマリ+インライン画像を返す。

例: 「火星の画像を見せて」「ハッブルの写真」「アポロの画像」

Args:
    query: 検索語(mars, jupiter, hubble, apollo など英語が確実)。
    limit: 返す画像件数(既定 3、最大 10)。
    show_inline: 画像をチャットにインライン表示するか(既定 True)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
show_inlineNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns structuredContent and content, implying a read-only search operation, and does not hint at side effects or mutations. It is transparent enough for a search tool.

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 very concise: two clear sentences about purpose and output, a list of examples, and a parameter list. No redundant or irrelevant information.

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?

The description covers purpose, output format, parameter semantics, and usage examples. This is sufficient for an agent to understand when and how to invoke the tool without ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description explains all three parameters: query as search term, limit as count with default (3) and maximum (10), and show_inline as a toggle for inline display. This fully compensates for the missing schema descriptions.

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 searches and displays images from the NASA Image & Video Library, with a specific scope (planets, satellites, missions) and explicitly differentiates output roles (structuredContent for LLM, content for chat). Examples further clarify intended use.

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 provides guidance on output format and parameter semantics, but does not explicitly contrast with sibling tools like search_space_videos or search_space_audio. The intended usage is implied via the name and description rather than directly stated.

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

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/loosephoto/space-finder-mcp'

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