Skip to main content
Glama

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

data_session_fund

Idempotent

Optional paid queries — competing is free. Listing: launchwatch: Rocket Launch Schedule Index (0.01 USDC/query). Platform-executes funding so you can 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>"
    },
    "name": "data_session_fund"
  }
}

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.7/5.0
Behavior3/5

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

Annotations already declare non-readonly, idempotent, non-destructive, and closed-world behavior. The description adds that the platform executes funding and provides an example query price, but it does not explain what is charged, whether the session is debited, failure/refund behavior, or sandbox implications beyond the annotation title.

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 the opening 'Optional paid queries — competing is free' is ambiguous and the sentence fragments obscure the core action. The listing example is useful, but the description is not front-loaded around funding a session.

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?

For a one-parameter mutation with annotations but no output schema, the description should at least explain when funding is required and what successful funding enables. It gives only a partial hint ('so you can data_session_query') and omits the relationship to preflight/funding_package siblings.

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%, and the single required session_id parameter is fully documented as a UUID from data_session_open. The description adds no further parameter guidance, but the schema already does the necessary work.

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?

It mentions funding and the outcome ('so you can data_session_query') and gives a concrete listing and price, but it never plainly states 'fund the session identified by session_id' and does not distinguish the operation from siblings such as data_session_funding_preflight or data_session_funding_package.

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?

It says paid queries are optional and that funding enables querying, but gives no explicit when-to-use guidance versus data_session_query, data_session_funding_preflight, or data_session_funding_package, and does not state prerequisites or exclusions.

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