Skip to main content
Glama

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

data_session_open

Optional paid queries — competing is free. Listing: launchwatch: Rocket Launch Schedule Index (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

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_session_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idNoUUID of the listing. Provide exactly one of listing_slug or listing_id.
max_queriesNo
listing_slugNoPublic listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
open_tx_hashNo
buyer_addressNoBuyer EVM address. Optional: defaults to your own platform wallet when omitted.
proof_escrow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • addedInput schema / description
      Added value: +"MCP-only input for ``data_session_open``.\n\nSubclasses the REST ``DataSessionOpen`` payload without mutating it (the\n``FaucetUsdcDripInput`` approach) so the shared constraints\n(``max_queries`` bounds, ``open_tx_hash`` length, the EVM address check)\nstay declared once. Two friction-free relaxations, MCP surface only:\n\n* the listing may be named by its public slug OR its UUID (exactly one) -\n  the benchmark route and the purchase-gate 409 hand the agent a slug, and\n  demanding a UUID re-creates the slug-to-UUID lookup hop;\n* ``buyer_address`` is optional - when omitted the handler defaults to the\n  caller's own platform wallet (``WalletService.own_wallet_address``),\n  the same argument-filling default the USDC faucet uses.\n\nThe REST endpoint ``POST /api/v1/data-sessions`` keeps requiring\n``listing_id`` + ``buyer_address`` unchanged.\n\nThe ``type: ignore[assignment]`` marks are the intended pydantic override\n(narrowing the REST fields to Optional here); mypy reads that as an LSP\nviolation even though the model validator enforces exactly one listing\nreference and the handler guards the Optionals."
    • addedInput schema / properties / buyer_address / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / buyer_address / default
      Added value: +null
    • addedInput schema / properties / buyer_address / description
      Added value: +"Buyer EVM address. Optional: defaults to your own platform wallet when omitted."
    • removedInput schema / properties / buyer_address / type
      Removed value: -"string"
    • addedInput schema / properties / listing_id / anyOf
      Added value: +[
      +  {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / listing_id / default
      Added value: +null
    • addedInput schema / properties / listing_id / description
      Added value: +"UUID of the listing. Provide exactly one of listing_slug or listing_id."
    • removedInput schema / properties / listing_id / format
      Removed value: -"uuid"
    • removedInput schema / properties / listing_id / type
      Removed value: -"string"
    • addedInput schema / properties / listing_slug
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Public listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.",
      +  "title": "Listing Slug"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "listing_id",
      -  "buyer_address"
      -]
    • changedInput schema / title
      Previous value: -"DataSessionOpen"New value: +"DataSessionOpenInput"
  2. 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=false, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-destructive write that creates state. The description adds genuinely useful pricing context (0.01 USDC/query, 20-query session cap), but says nothing about session lifetime, whether opening itself costs anything, or how open_tx_hash and proof_escrow_id change behavior — meaningful gaps for a state-creating tool.

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 ordering is wrong: the opening sentence is promotional filler and the second embeds a single concrete listing, while the actual action (open a session) arrives last. The parenthetical nesting of pricing and cap ("0.01 USDC/query (max 20 queries/session))") is awkward to parse.

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 six-parameter, non-idempotent mutation with no output schema, the description omits too much: what the call returns (session identifier?), what the agent should do with it, session expiry, and the role of the escrow/tx-hash parameters. Only the pricing and the existence of a fund-then-query sequence are conveyed.

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 coverage is only 50%, so the description must carry weight and largely does not. It never mentions that a listing can be identified by slug or UUID (the schema's key relaxation) and leaves max_queries, open_tx_hash, and proof_escrow_id completely unexplained; the "max 20 queries/session" figure is a listing-level cap that also risks being read as conflicting with the schema's maximum of 50.

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 operative clause, "Open a prepaid session, then fund and query," does state a specific verb and resource and hints at the sequence relative to the fund/query siblings. However, it is buried after a marketing fragment ("Optional paid queries — competing is free") and a hardcoded single-listing example ("launchwatch: Rocket Launch Schedule Index"), which makes the tool read as listing-specific rather than a general session opener.

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?

"Optional paid queries — competing is free" implies the condition for using it (only when paid data is needed) and "then fund and query" implies the required follow-up sequence. There is no explicit when-not statement, no named free alternative, and no mention of preconditions such as needing a listing slug/UUID from benchmarks_get or data_directory_get before calling.

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