Skip to main content
Glama

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

data_session_fund

Idempotent

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

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

Annotations already declare not-read-only, not-destructive, idempotent and closed-world, so the safety profile is covered. The description adds one genuinely useful fact — the platform executes the funding rather than the caller signing — but says nothing about what gets debited, whether the 0.01 USDC is per query or per session, caps or minimums, or how funds come back (siblings for mark_refunded exist). For a money-moving tool that is a real gap.

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 lead clause 'Optional paid queries — competing is free' is cryptic and front-loads marketing rather than the action. The listing detail and the funding statement are useful and packed into few tokens, but the information order buries the actual verb.

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?

This is a non-destructive mutation that moves funds, with no output schema and no annotation explaining monetary consequences. An agent cannot tell from the definition what a successful call returns (funding status, signing payload, escrow state) or what limit applies, which is not adequate for a fund-moving tool of this complexity.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains session_id as a UUID from data_session_open, so the baseline is 3. The description adds no meaning about the parameter — e.g., whether the session must be open and unfunded, or what happens if it is already funded.

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 never plainly says 'fund a data session'; the agent has to piece it together from 'Optional paid queries' and 'Platform-executes funding so you can data_session_query.' It does tie the tool to a concrete use (paying for a 0.01 USDC/query listing) and to the downstream sibling data_session_query, but the verb+resource statement is oblique.

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 when-to-use condition (only for paid listings, not for free competition), and 'so you can data_session_query' implies the ordering. However, nothing states when NOT to fund, and it never distinguishes this from the funding siblings (data_session_funding_preflight, data_session_funding_package), so the agent must infer the routing.

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