Skip to main content
Glama

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

data_session_query

Optional paid queries — competing is free. Listing: spaceweather: Solar & Geomagnetic Activity Index at 0.01 USDC per query (max 20 queries/session). Sequence: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "query": "<query>"
    },
    "name": "data_session_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
session_idYesUUID of a data session you opened (from data_session_open).
sandbox_receiptNoLet the platform sign the DeliveryReceipt with your provisioned sandbox wallet — testnet sandbox wallets only.
delivery_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent, closed-world), and the description adds genuinely new behavior: per-query cost of 0.01 USDC and a hard cap of 20 queries per session. It does not explain what happens when the quota or balance is exhausted, but the pricing and rate-limit disclosure is exactly the kind of context annotations cannot carry.

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?

Compact at three fragments with no wasted verbosity, and the pipeline ordering is placed prominently. However, the lead is front-loaded with the vague 'Optional paid queries — competing is free' rather than the action, so the most useful information (the sequence) is not first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent, non-read-only tool with five parameters, 40% schema coverage, and no output schema, the description is thin on mechanics: no mention of what a successful query returns, how the delivery receipt is produced, or what occurs on insufficient funds. It does supply prerequisites and cost, which keeps it from being inadequate, but the mutation-side behavior remains unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40% of five parameters, so the description needs to compensate and does not. It never mentions 'query', 'k', or 'delivery_receipt'; the identifiers it does cite (buyer_address, open_tx_hash) belong to sibling tools rather than this tool's own inputs, so the agent gains no meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The lead phrase 'Optional paid queries' names an activity but not a specific verb+resource; the resource ('data session') and the actual action only become clear from the pipeline sequence ending in data_session_query. It never states plainly 'run a query against a funded session', and the aside 'competing is free' muddies the opening.

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 explicit chain (data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query) tells the agent exactly when this tool becomes available and what must precede it, which is strong ordering guidance across siblings. It stops short of stating exclusions or failure conditions (e.g. what to do if the session is unfunded).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources