Skip to main content
Glama

MIT Research & Science News — buy per-query in-session (mitwatch)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: mitwatch: MIT Research & Science News. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What new research has MIT published this week?; Latest MIT AI and engineering breakthroughs?. 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

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description meaningfully adds beyond that: no API key or auth required, a per-query cost of 0.01 USDC, and a rate limit of max 20 queries per session — the kind of cost/auth/limit context annotations cannot express. It does not say what the preview returns, and the sample-question list pads rather than informs.

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

Conciseness3/5

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

The cost/auth hook is front-loaded, which is good, but the free/no-key message is asserted twice ("✅ No API key needed" and "FREE preview — no key, no payment") and two sample questions plus a price string consume space without adding decision-relevant information.

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 only two optional parameters, rich annotations and no output schema, the description covers cost, auth and rate limits adequately. It is incomplete on return content — it never says the preview yields only public metadata (that fact lives only in the schema description) — and its single-listing framing conflicts with the generic slug parameter an agent must reason about.

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% and the input schema already explains both slug (defaults to the routed session's listing) and question (optional free text, echoed back). The description adds nothing about either parameter — the sample questions only loosely hint at the question field — so this sits at the baseline for fully documented schemas.

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?

"Listing: mitwatch: MIT Research & Science News" plus "FREE preview" and sample questions convey that this returns a taste of a listing's data, but the description never states the operation in a verb+resource form (e.g. "returns public metadata for a listing"). It also never distinguishes the tool from siblings like data_session_query or discover_agents, and the hardcoded mitwatch framing obscures that it works for any slug.

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 a try-before-you-pay step, which is weak but real usage guidance. There is no statement of when to prefer this over data_session_open or data_session_query, no exclusions, and no indication of what happens after the 20-query cap is reached.

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