Official DeepMind Blog — Gemini & AI Releases (deepmindwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: deepmindwatch: Official DeepMind Blog — Gemini & Google AI Model Releases. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the newest DeepMind blog announcements?; Latest Gemini model releases from DeepMind?. 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 9, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context (no API key or payment required, 20 queries/session cap), but its pricing line ("0.01 USDC/query") sits uneasily next to "FREE preview — no payment" and it never states what the preview actually returns.

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 lead "✅ No API key needed" is repeated later as "FREE preview — no key, no payment," and roughly half the text is sample-question filler rather than operative information. It is short but redundant and front-loads promotional framing ahead of the tool's function.

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?

This is a simple two-optional-parameter, read-only tool with full schema coverage and no output schema, so less is required. Still, the description never says what a "preview" returns or how it differs from a paid query, and the price/free ambiguity is left unresolved for the agent.

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% and both optional parameters (slug, question) are documented in the schema, including that the question is echoed back. The description adds essentially nothing about parameter semantics beyond the sample questions loosely hinting at the question field, so baseline 3 applies.

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 positions the tool as a "FREE preview" of the "deepmindwatch" listing, but most of the text is marketing copy about the listing itself (blog coverage, price, sample questions) rather than a statement of what the tool does. There is no clear verb or description of the result (the actual scope, "public metadata only," lives in the schema, not the description).

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?

It suggests trying a sample question, which implies usage, but gives no routing guidance against siblings like data_session_open or data_session_query, no statement of when this free preview is the right choice versus paying for a full query, and no prerequisites beyond "no key needed."

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

All Official DeepMind Blog — Gemini & AI Releases (deepmindwatch) 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?