Skip to main content
Glama

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

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: awswhatsnew: AWS cloud service announcements & feature updates. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What new AWS service announcements were published recently?; Any new Amazon Bedrock or SageMaker feature updates?. FREE preview — no key, no payment. Try one of the sample questions now.

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

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

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 already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety bar is low. The description adds useful disclosure — no API key, 0.01 USDC/query pricing, 20-query session cap — but the pricing line sits awkwardly against the repeated 'FREE' claims, creating internal ambiguity about whether calls cost anything.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It leads with a decorative '✅ No API key needed' and then repeats the same point later as 'no key, no payment', wasting space on duplication. The two sample questions occupy substantial length without advancing understanding of the tool, and the actual purpose is buried mid-string.

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 2-optional-param read-only tool with no output schema, the description covers cost, session limits, and sample usage, which is broadly adequate. However, it omits what the preview actually returns (the schema's 'public metadata only' note carries that burden) and provides no fallback guidance for after the 20-query cap.

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%, so both slug and question are fully documented in the schema, making 3 the baseline. The sample questions illustrate how to populate the question parameter, which is a small value-add, but the description never explains slug or the routing behavior beyond what the schema already states.

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 identifies a resource ('Listing: awswhatsnew: AWS cloud service announcements') and labels it a 'FREE preview', but never states a clear verb for the tool itself — it reads more like marketing copy for a listing than a definition of an operation. An agent can infer this previews a data listing, but the intent is only implied and no sibling (e.g., data_session_query, discover_agents) is named for contrast.

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?

'FREE preview — no key, no payment. Try one of the sample questions now' gives implied guidance to use this as a free trial, and the query cap of 20/session hints at a preview tier. But it never states when to prefer this over the paid data_session_query sibling or what happens after the preview ends, leaving routing to inference.

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