Skip to main content
Glama

AWS Cloud Service Updates & Announcements — buy per-query (awswhatsnew)

data_session_query

Optional paid queries — competing is free. Listing: awswhatsnew: AWS cloud service announcements & feature updates 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.2/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two genuinely useful behaviors: each query costs 0.01 USDC and a session caps at 20 queries. This explains the non-idempotent hint (repeat calls spend money). It omits what happens when the session is unfunded or exhausted, and does not describe what a query returns.

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 and dense, but the front-loaded content is pricing and a listing blurb rather than the tool's action, so the reader must reconstruct the purpose. The sequence sentence is useful context but mostly describes sibling tools. Nothing is verbose, yet the emphasis is misallocated for a tool definition.

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 5-parameter, non-idempotent, paid operation with no output schema, the description should explain what comes back (results? a signed delivery receipt?) and how k and delivery_receipt affect the call. Instead it covers workflow ordering and cost only, leaving the query payload and response contract undocumented.

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% — session_id and sandbox_receipt are documented in the schema, but k, query, and delivery_receipt are not. The description adds no meaning for any of these (e.g., what k controls, what a delivery_receipt string is for), so it fails to compensate for the coverage gap. The only parameter-adjacent text ("self-sign from buyer_address", "open_tx_hash") belongs to other tools in the sequence, not this one.

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 conveys that this is a paid query against a data session ("0.01 USDC per query") but never states the operation plainly — the actual phrasing "Run a prepaid query against a funded data session" lives only in the schema description. It leads with pricing and a listing name instead of the verb+resource, so the purpose is inferable rather than stated.

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

Usage Guidelines4/5

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

The explicit sequence (data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query) tells the agent exactly what must precede this call, which is strong prerequisite guidance. It also notes queries are optional because "competing is free," implying a no-cost alternative. It stops short of naming sibling alternatives such as data_preview or benchmarks_search for non-session lookups.

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