Skip to main content
Glama

Rocket Launch Schedule (SpaceX, Falcon, Electron) — buy per-query in-session (launchwatch)

data_session_query

Optional paid queries — competing is free. Listing: launchwatch: Rocket Launch Schedule 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.1/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, idempotent=false, destructive=false, openWorld=false); the description adds real behavioral context on top: the per-query price of 0.01 USDC and the 20-queries-per-session cap, plus the requirement that the session be funded first. It does not say what happens when the cap is hit or whether a failed query still consumes prepaid funds, which keeps it short of a 5.

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 compact and front-loaded, but the opening clause 'Optional paid queries — competing is free' is vague and the listing/sequence fragments are telegraphic rather than readable sentences. The sequencing content earns its place; the marketing-style lead-in does not.

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?

With no output schema, five parameters, and a non-idempotent paid mutation, the description should explain return behavior and failure/cost implications. It covers prerequisites and price adequately but leaves an agent guessing about what a query returns and what happens to prepaid funds on error.

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% across 5 parameters, so the description needs to compensate and does not. It explains none of the tool's own parameters — the meaning of k, the free-text query, or delivery_receipt are untouched; the identifiers it does mention (buyer_address, open_tx_hash) belong to sibling tools, not to this input 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 description frames the tool as 'Optional paid queries' and names a concrete listing (launchwatch: Rocket Launch Schedule Index) at a price, which tells an agent this spends prepaid balance on a query. However, it never states the core verb+resource plainly ('run a query against a funded session') — that clarity only appears in the schema description, not here. It is distinguishable from siblings mainly through the prerequisite chain rather than a direct statement of what it does.

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

Usage Guidelines3/5

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

The explicit ordering data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query is genuinely useful when-to-use context, including the self-sign-from-buyer_address and open_tx_hash hints. What is missing is a clear statement of when NOT to call it (e.g., unfunded session, free alternatives) beyond the oblique 'competing is free', which refers to listings, not tools.

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