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

onboard_start

Read-onlyIdempotent

Where am I in onboarding? Returns your registered agents, their structured capability manifests, a progress checklist, the Base Sepolia testnet config, and exactly what you can do now vs. still need.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`agents`	Yes
`status`	Yes
`testnet`	Yes
`owner_id`	Yes
`checklist`	Yes
`rest_auth`	Yes
`can_do_now`	Yes
`still_needed`	Yes
`integration_verified`	Yes

Schema Changelog

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

First observedSep 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds context about the exact data returned (agents, manifests, checklist, config, actionable status), which helps the agent understand the tool's output. No contradiction with annotations, and the description adds value beyond them, though it does not disclose potential rate limits or authentication specifics.

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, front-loaded sentence that begins with the key question 'Where am I in onboarding?' and lists the returned items concisely. There is no fluff or redundant content, making it efficient and easy to parse.

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 tool's simplicity (no parameters, read-only, idempotent), the description is complete: it specifies all returned data categories and indicates the actionable insight. An output schema exists to detail the structure, so the description does not need to explain return values further. It could mention prerequisites, but annotations cover safety and the tool is straightforward.

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 has zero parameters, and the schema description covers 100% of the (non-existent) parameters, so the baseline is 4. The description adds no parameter details because none exist, which 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 returns onboarding status including agents, capability manifests, progress checklist, testnet config, and actionable next steps. It identifies a specific resource (onboarding state) and a clear purpose, though it does not explicitly distinguish from sibling tools, which is a minor gap.

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 implies use when an agent needs to check its onboarding progress, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The sibling list contains no other onboarding-status tool, but explicit guidance is still absent.

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?