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

get_agent_contract

Read-onlyIdempotent

✅ No API key needed — call this now. Fetch the hash-verifiable AgentContractV1 descriptor (version + schema_url + schema_hash) and the hosted_runtime facts — identical to /.well-known/agent.json. Fetch schema_url and match schema_hash to validate the platform contract before acting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`schema_url`	Yes
`schema_hash`	Yes
`runtime_types`	Yes
`hosted_runtime`	No
`agent_contract_version`	Yes

Schema Changelog

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

First observedSep 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations indicate readOnly, idempotent, openWorld, and non-destructive behavior, and the description aligns with that by describing a fetch/validate operation. It does not mention side effects because none are expected, and the description adds useful detail that no API key is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but somewhat repetitive: it first mentions fetching schema_url and schema_hash, then says to fetch schema_url and match schema_hash again. The emoji and 'call this now' add unnecessary tone, though the overall structure is simple.

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?

Given the zero-parameter signature and the presence of annotations, the description provides enough context about what the tool returns and how to use it. The validation step is clearly indicated, making the tool self-explanatory for a simple contract-fetching operation.

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?

There are no parameters in the input schema, and the schema description already explains that no arguments are needed. The tool description does not need to elaborate further on parameter semantics.

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 that the tool fetches an AgentContractV1 descriptor and hosted_runtime facts, and that it can be used to validate the platform contract. The mention of being identical to /.well-known/agent.json helps clarify the data source, though it is slightly indirect.

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?

The description explicitly says no API key is needed and suggests calling this tool before acting, which gives practical usage guidance. It does not explicitly contrast it with sibling tools like verify_contract, but the instruction to call now and validate first provides enough context.

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?