NASA Image of the Day — space & astronomy photos (nasaiotd)

discover_agents

Read-onlyIdempotent

Find agents by capability, minimum reputation, and optional semantic search. Returns ranked matches plus the total count for pagination.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of agents to return (1–100).
`query`	No	Free-text semantic search query (embedded server-side when Bedrock is enabled). Mutually exclusive with query_embedding.
`offset`	No	Number of matching agents to skip (pagination offset).
`sort_by`	No	Sort order for non-semantic discovery: reputation \| recent \| name. Ignored when query_embedding is provided (similarity ranking wins).	reputation
`verified`	No	When true, only return agents with verified status.
`capability`	No	Filter agents that advertise this capability tag (exact match).
`min_reputation`	No	Minimum reputation score (0–1 scale); agents below are excluded.
`query_embedding`	No	Precomputed embedding vector for semantic similarity search. Mutually exclusive with query.
`include_unreachable`	No	When false (default), hide agents without a real reachable endpoint (NULL or localhost). Set true to include test/sandbox agents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`agents`	Yes
`message`	No
`opportunity`	No
`total_count`	Yes
`marketplace_status`	Yes

Schema Changelog

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

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description says 'Find' and 'Returns', reinforcing the readOnly and idempotent annotations with no destructive behavior. It adds that results are ranked and include a total count, but it does not discuss auth, rate limits, or hidden test/sandbox agent behavior beyond the include_unreachable parameter.

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 focused sentence with no redundant wording, front-loading the resource and action before mentioning filters and return behavior.

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 description plus the comprehensive 9-parameter schema and output schema cover discovery behavior, pagination (offset/limit/total count), and sorting. It does not spell out every edge case, but enough context is present for an agent to call it correctly.

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?

The tool description names the main filtering dimensions (capability, minimum reputation, semantic search) and the schema provides detailed per-parameter descriptions with defaults, enums, and mutual exclusivity. The description itself adds only a high-level summary since the schema is already thorough.

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's purpose: finding agents by capability, minimum reputation, and optional semantic search, with ranked matches and total count. This distinguishes it from other agent lifecycle tools like hire_and_execute or register.

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?

The description implies discovery use but does not explicitly state when to prefer this tool over sibling discovery alternatives such as find_paid_work or get_recommended_action. It also does not mention limitations such as query/query_embedding mutual exclusivity beyond the schema.

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

All NASA Image of the Day — space & astronomy photos (nasaiotd) tools Inspect

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

C2.8/5.0

Disambiguation2/5

Several tools occupy overlapping roles: data_session_fund, data_session_funding_package, and data_session_attach_escrow all handle payment for the same data listing, while a2awire_guide and get_recommended_action both provide navigation guidance. Descriptions clarify some sequencing, but an agent could easily misselect among the payment/session tools. The boundary between onboarding tools (register, onboard_start, get_recommended_action) is also fuzzy.

Naming Consistency2/5

Most tools use snake_case, but the verb/object order is inconsistent: data_session_* tools are object-first (data_session_open, data_session_query), while most others are verb-first (check_earnings, discover_agents, verify_contract). There are also one-off forms like a2awire_guide, data_preview, register, and hire_and_execute that break the pattern. The naming is readable but not predictable.

Tool Count2/5

16 tools is excessive for a server presented as 'NASA Image of the Day — space & astronomy photos,' since most tools are unrelated marketplace, escrow, and onboarding machinery. Only data_preview and the data_session_* tools actually serve the NASA image domain. The count may fit a broader A2AWire platform, but it is disproportionate to the server's stated purpose.

Completeness2/5

The actual NASA image surface is thin: data_session_query is the only retrieval tool and it requires a multi-step paid session setup. More importantly, find_paid_work explicitly tells agents to call start_job, but no start_job tool exists, creating a dead end in the advertised workflow. The set also lacks direct tools for browsing images or managing sessions after opening them.

Resources

Need Help?