Skip to main content
Glama

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

data_session_open

Optional paid queries — competing is free. Listing: awswhatsnew: AWS cloud service announcements & feature updates (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. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare it is a non-read-only, non-destructive, non-idempotent operation; the description adds pricing (0.01 USDC/query), a per-session query ceiling (20), and the prepaid funding model, which are real behavioral facts not in the annotations. It does not disclose what opening actually commits (e.g. whether funds are drawn at open time, what happens on timeout, or that repeated calls create separate sessions), so the mutation semantics remain partly opaque.

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 short but poorly ordered: a confusing tagline and a hard-coded listing advertisement precede the actual operation, so the essential action is buried at the end. Every sentence is short, yet the first sentence does not earn its place.

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, the description does not say what a successful open returns (session id, expiry, balance) which an agent needs before calling data_session_fund. It does supply pricing and the query cap, which is meaningful context for a paid, stateful tool, but the open-then-fund handoff is only gestured at rather than described.

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?

The description never mentions any of the six parameters. At 50% schema coverage, the slug-vs-UUID exclusivity and buyer_address default are documented only in the schema's verbose input description, and max_queries, open_tx_hash, and proof_escrow_id (including how it relates to data_session_attach_escrow) are unexplained anywhere. The narrative does not compensate for the coverage gap.

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 final clause ("Open a prepaid session, then fund and query") names the verb-resource, but the opening sentences spend most of their words on pricing and a specific listing (awswhatsnew) rather than on the operation itself. An agent must read to the end to learn this opens a session, and the lead-in "Optional paid queries — competing is free" reads as marketing copy, not purpose.

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 ordering "open, then fund and query" implies the workflow and is genuinely useful, but it never says when to choose this tool over the many siblings (data_session_funding_package, data_session_funding_preflight, data_session_attach_escrow) or what happens if a session already exists. No exclusions or prerequisites are stated.

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