Skip to main content
Glama

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

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: launchwatch: Rocket Launch Schedule Index (0.01 USDC/query). Returns fund instructions after data_session_open.

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>"
    },
    "name": "data_session_funding_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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, so the safety profile is covered structurally. The description adds genuinely new context — that this is the paid path, a sample price of 0.01 USDC/query, and that it must follow data_session_open — but says nothing about what the returned instructions contain or what happens if the session is unfunded or expired.

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?

It is short, but poorly front-loaded: the opening sentence is a pricing/marketing pitch rather than the tool's action, and the single example listing ('launchwatch: Rocket Launch Schedule Index') is illustrative noise for an agent deciding whether to call this tool. The one operative sentence comes last.

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 one-parameter, read-only, idempotent tool with full schema coverage and no output schema, the description needs mainly to nail purpose and sequencing, which it does partially via 'after data_session_open'. It falls short on distinguishing the funding-package step from adjacent funding tools, which is the main ambiguity an agent would face in this cluster.

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 coverage is 100% and the single session_id parameter is fully documented with a UUID format and its origin. The description's 'after data_session_open' merely restates that provenance, adding no new semantic detail. Baseline 3 applies when the schema carries the parameter documentation.

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?

Only the final clause ('Returns fund instructions after data_session_open') describes the actual operation; the preceding sentences pitch a marketplace listing rather than state a verb+resource. An agent can guess this fetches payment/funding instructions for a session, but the core purpose is buried and not distinguished from siblings like data_session_funding_preflight or data_session_fund.

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?

'Optional paid queries — competing is free' implies a conditional context (pay only when you want the paid data), and 'after data_session_open' implies ordering. However, there is no explicit statement of when to call this versus data_session_funding_preflight, data_session_fund, or data_session_attach_escrow, leaving the routing decision to inference.

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