Skip to main content
Glama

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

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: spaceweather: Solar & Geomagnetic Activity Index. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What is the current Kp index and is a geomagnetic storm underway?; Is there a solar flare in progress right now?. FREE preview — no key, no payment. Try one of the sample questions now.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered by structured data. The description adds genuinely useful context beyond that: no API key required, no payment for the preview, and a cap of 20 queries per session. However, the conflicting price statement undercuts the 'free' claim, and nothing is said about what the response contains.

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 text is short, but it is structured as promotional copy (checkmark emoji, price line, two sample questions, repeated 'no key, no payment' twice) rather than front-loading the operation's purpose. The 'FREE preview' statement is stated twice in redundant forms, and no sentence states what the call returns.

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

Completeness2/5

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

There is no output schema, so the description bears responsibility for explaining what a preview yields — presumably the listing's public metadata, pricing, and sample capabilities — and it never says. Combined with the ambiguous paid-vs-free messaging, an agent lacks what it needs to decide between data_preview and data_session_query for the same listing.

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 slug default (routed session's listing) and the optional echoed-back question are both fully documented in the schema. The description adds nothing about either parameter beyond loosely hinting that the sample questions are values for the 'question' field. Baseline 3 applies when the schema carries the semantics.

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 description identifies the target listing ('spaceweather: Solar & Geomagnetic Activity Index') and frames the tool as a 'FREE preview', but it never states in plain terms what the tool actually does or returns — a specific verb/object like 'returns public metadata and pricing for a listing without a session' is absent. The mixed signals ('Price 0.01 USDC/query' followed immediately by 'FREE preview — no key, no payment') leave the agent unsure whether this is a free call or a paid query. It also does not name a sibling such as data_session_query to draw the boundary.

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?

There is no explicit when-to-use guidance — nothing says to call this before data_session_open or data_session_query, or that it is for exploring a listing before funding a session. The sample questions ('What is the current Kp index...') imply topical use but do not function as selection guidance. The 'max 20 queries/session' cap hints at a trial constraint, yet no exclusion or alternative is offered.

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