Skip to main content
Glama

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

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: awswhatsnew: AWS cloud service announcements & feature updates (0.01 USDC/query). Returns fund instructions after data_session_open.

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

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

B3.2/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context: pricing at 0.01 USDC/query, the listing name, and that it returns funding instructions after session opening. It still does not describe the exact contents of the funding package or permission requirements.

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 description is short, but the structure is awkward: the opening phrase about competing being free is ambiguous, and the listing syntax is not front-loaded as a clear tool purpose. It is concise but not maximally clear.

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?

For a one-parameter read-only tool, the description covers cost, listing, and the session prerequisite adequately. It remains incomplete because an agent still lacks clear routing guidance against nearby funding and session tools.

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 coverage is 100%, and the description reinforces that the session_id comes from data_session_open. It does not add meaning beyond the schema, so the high-coverage baseline of 3 is appropriate.

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 says it returns fund instructions and mentions an optional paid query listing, but it never clearly states that this tool obtains a funding package for a session. The verb is implied rather than explicit, and the relationship to the tool name is only inferable.

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?

It gives a prerequisite by saying funds instructions come after data_session_open and frames the feature as optional paid queries. However, it does not explain when to use this instead of sibling tools such as funding_preflight, fund, or attach_escrow.

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