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

data_session_fund

Idempotent

Buy per-query access to live data listings — first taste free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Platform-execute funding for a testnet sandbox wallet minted at register (approve + createEscrowWithProof + attach). Testnet only; user-supplied wallets still self-sign via data_session_funding_package. Not guest-callable. No REST analogue.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	UUID of a data session you opened (from data_session_open).

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavioral details: requires an agent API key, platform-executes the funding flow (approve + createEscrowWithProof + attach), is testnet-only, and is not guest-callable. It also notes there is no REST analogue. The description does not contradict the annotations.

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 dense but every clause earns its place: purpose, free alternative, authentication, platform flow, testnet restriction, alternative path for user-supplied wallets, and guest-callability. Information is front-loaded and no filler or redundancy appears.

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?

Given the tool has one fully documented parameter and no output schema, the description covers everything an agent needs to invoke it correctly: authentication, target session context, platform wallet flow, network restriction, and when to choose the sibling tool instead. This is highly complete for its complexity.

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%: the only parameter, session_id, is fully described as a UUID from data_session_open. The description adds no additional parameter-level meaning, but none is needed since the schema already fully documents the parameter.

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 clear verb-resource pair: 'Buy per-query access to live data listings.' It also differentiates itself from siblings by referencing data_preview for the free taste and data_session_funding_package for user-supplied wallets, so an agent can distinguish this tool from near-names without opening schemas.

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?

The description gives explicit context and alternatives: use this for platform-execute funding on a testnet sandbox wallet; use data_session_funding_package for user-supplied wallets that self-sign; use data_preview for the first free taste. It also states it is testnet-only and not guest-callable, so the agent knows when this tool is applicable.

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?