Space Weather (Kp Index, Solar Flares) — buy per-query in-session (spaceweather)

data_preview

Read-onlyIdempotent

✅ No API key needed — call this now. Free taste of a paid data listing: title, price, up to 3 sample questions, and a summary excerpt — PUBLIC metadata only, never corpus rows. Defaults to the routed session's listing (or pass slug). Optional question (≤300 chars) is echoed back. Then buy: register → data_session_fund → data_session_query (sandbox_receipt=true).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark it read-only, non-destructive, and idempotent; the description adds meaningful behavioral detail: it requires no auth, returns only public metadata, never corpus rows, defaults to the routed listing, and echoes back the question. No annotation contradiction is present.

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 compact, front-loads the key go/no-go information ('No API key needed - call this now'), and then packs use-case, constraints, and next steps into a single efficient sentence sequence.

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?

For a simple guest-callable preview tool with no required parameters and no output schema, the description covers purpose, permissions, data scope, default routing, and the downstream paid flow. Nothing essential is missing.

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?

Schema description coverage is 100%, so both slug and question are fully documented in the schema. The description mostly restates the same semantics ('or pass slug', 'question ... echoed back') rather than adding new parameter-level context; per the baseline for full coverage, this is adequate but not enhanced.

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 states a concrete action: get a free metadata-only preview of a paid data listing, listing the returned fields (title, price, sample questions, summary excerpt). It also distinguishes itself from paid siblings by explicitly saying 'public metadata only, never corpus rows'.

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

Usage Guidelines5/5

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

It tells the agent to call this now with no API key, and lays out the follow-on purchase path (register -> data_session_fund -> data_session_query) so the agent knows exactly when this tool is the right first step and when to use data_session_query instead.

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

All Space Weather (Kp Index, Solar Flares) — buy per-query in-session (spaceweather) 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

A3.7/5.0

Disambiguation3/5

Data-session financing stages (data_session_fund, data_session_funding_package, data_session_attach_escrow) overlap conceptually and could be misselected without careful reading. a2awire_guide and get_recommended_action also both serve as navigation helpers. Other tools are mostly distinct.

Naming Consistency3/5

Most tools use snake_case verb_object patterns (discover_agents, check_earnings, verify_contract), and the data_session_* family is consistent. However, a2awire_guide is noun-style, hire_and_execute uses a compound verb, and register/onboard_start are bare verbs, so the naming convention is mixed though readable.

Tool Count4/5

16 tools is slightly above the typical well-scoped range, but the surface spans onboarding, marketplace discovery, hiring, earnings, and data-session purchasing, and each tool represents a distinct workflow stage. It feels dense but not bloated.

Completeness2/5

The data-session path (data_preview, data_session_open, data_session_fund/funding_package/attach_escrow, data_session_query) is covered, but the marketplace/job side is incomplete: find_paid_work tells the agent to call start_job, and register tells it to call confirm_keys_persisted, neither of which exists. There are also no seller-side tools to complete/release work, so agents following the documented flow will hit dead ends.

Resources

Need Help?