Official Google Product Announcements — buy per-query in-session (googleblogwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: googleblogwatch: Official Google product announcements & releases. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What did Google announce this week?; Show the newest Google product launches and feature releases. 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

Name	Required	Description	Default
`slug`	No	Public listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
`question`	No	Optional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 10, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful auth-free detail but then muddles billing: "Price 0.01 USDC/query (max 20 queries/session)" directly conflicts with "FREE preview — no key, no payment," which could make an agent believe a preview call costs money. That internal inconsistency works against behavioral clarity rather than for it.

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?

The text is mostly promotional filler: "no API key needed" is stated twice, sample questions take up space, and per-listing pricing is irrelevant to invoking a free preview. The one operationally meaningful clause is buried mid-paragraph rather than front-loaded.

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 two-optional-parameter preview tool with no output schema, the description should say what a preview returns (listing metadata, echoed question) and how it relates to the paid query path. Instead it repeats listing marketing and omits any description of the response, leaving the agent dependent on the schema's parenthetical.

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 description coverage is 100%, with both slug and question fully documented in the schema, so the baseline is 3. The description's mention of sample questions loosely maps to the question parameter, but the hardcoded single listing name could mislead an agent into thinking slug is fixed rather than a free parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states a clear verb+resource operation; the only functional statement is "FREE preview — no key, no payment," which largely restates the title "Preview Data Listing (Free)." The bulk of the text advertises one specific listing (googleblogwatch) and its pricing rather than explaining what the tool actually does, leaving the agent to infer from the schema that it returns public listing metadata.

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

Usage Guidelines2/5

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

"Try one of the sample questions now" implies passing a question, and "No API key needed" implies guest usage, but there is no guidance on when to use this versus data_session_open, data_session_query, or data_session_fund — all of which appear as siblings. No when-not-to-use conditions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Official Google Product Announcements — buy per-query in-session (googleblogwatch) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?