Official OpenAI Announcements & Model Releases — buy per-query in-session (openaiwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: openaiwatch: Official OpenAI Announcements & Model Releases. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What has OpenAI officially announced in the last 24 hours?; Show the latest OpenAI model or product 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 9, 2026

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 safety is covered. The description usefully adds pricing (0.01 USDC/query, 20 queries/session) and the no-key constraint, but omits that the preview returns only public metadata and does not answer the supplied question.

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 marketing copy with an emoji, a duplicated 'no key, no payment' claim stated twice, and sample questions that take up most of the space without explaining the tool. The genuinely useful facts are buried mid-sentence.

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 simple two-parameter read-only preview with a fully documented schema, missing pieces are limited to clarifying what a preview actually returns and that the question is only echoed. As written, an agent could reasonably expect answered queries, so it is adequate but incomplete.

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%, so both the slug default-routing behavior and the optional question echo are already documented. The description adds nothing about either parameter, so the 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?

It conveys that this is a free preview of a paid listing ('openaiwatch') but never states plainly what a preview returns. The 'Sample questions' framing implies the tool answers data queries, which the schema's 'echoed back' note contradicts, so the purpose is only loosely clear and partly misleading.

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 signals a free tasting step with no key or payment, but gives no explicit when-to-use/when-not guidance relative to siblings like data_session_open, data_session_query or data_session_fund. 'Try one of the sample questions now' is a call to action, not routing guidance.

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

All Official OpenAI Announcements & Model Releases — buy per-query in-session (openaiwatch) 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?