Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: msrcwatch: Microsoft MSRC Security Updates. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What is the latest Microsoft security update bulletin?; Were there any out-of-band Windows security releases this month?. 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 7, 2026

TDQS

C2.7/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 the description usefully adds concrete behavior: no API key required, 0.01 USDC per query price, and a 20-queries-per-session cap. However, it omits the most important behavior — that 'question' is only echoed back rather than answered — which the sample-question prompt actively obscures.

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 promotional rather than informational: a checkmark emoji, repetition of the free/no-key claim twice, and a sales-style closing CTA. The single most useful fact (what the tool returns) is absent while redundant payment messaging takes its place.

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?

With two optional params, no output schema, and strong read-only annotations, the bar is low, and price/rate-limit/auth details are covered. Still, an agent reading only the description would not know the return is a metadata preview with no real answer, which is the gap that matters most for correct invocation.

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' (routing default) and 'question' (echoed free-text, max 300) are fully documented in the schema, and the schema-level description clarifies 'public metadata only'. The description adds only illustrative question content and no format or routing detail beyond the schema, 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 identifies the listing ('msrcwatch: Microsoft MSRC Security Updates') and labels itself a 'FREE preview', so the resource is nameable. But it never states the actual operation — that it returns public listing metadata — and the 'Sample questions ... Try one of the sample questions now' framing makes it read like a query tool, which blurs its identity against siblings like data_session_query.

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?

There is a call-to-action ('Try one of the sample questions now') but no guidance on when to choose this over data_session_open or data_session_query. The agent is never told this is the pre-purchase step before funding a session.

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

All Microsoft Windows Security Updates (MSRC CVRF) — buy per-query in-session (msrcwatch) 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?