Skip to main content
Glama

Science News Tracker — latest research & discovery headlines (scinews)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: scinews: Latest science news & breakthrough headlines. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the latest science news headlines?; What science breakthroughs were announced today?. 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

C2.4/5.0
Behavior2/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior; the description adds useful auth/cost context ('No API key', 'no payment') and a session limit. However, it contradicts itself by also stating 'Price 0.01 USDC/query' and implies the tool answers questions, whereas the schema says the question is only echoed back in a public-metadata preview.

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 front-loaded checkmark and repeated 'No API key needed'/'FREE preview — no key, no payment' spend words on reassurance rather than defining the operation. The pricing and sample-question sentences are not only redundant but introduce ambiguity, so the text is not tightly structured.

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 simple two-parameter preview tool with no output schema, the description should clarify that it returns public metadata and does not execute the sample questions. Instead it emphasizes a paid-query price and invites question answering, leaving the return behavior ambiguous despite the schema's brief 'public metadata only' note.

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 slug and question are already documented, including the slug default and echoed-question behavior. The description's sample questions loosely illustrate the question field but add no meaning about slug or output beyond the schema; baseline 3 is appropriate.

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 names a free preview of the scinews listing, but never states the actual operation: that it returns public listing metadata rather than answering the sample questions. The sample questions and paid-query pricing line blur whether this is a preview or a data query, so an agent cannot confidently distinguish it from 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?

It advertises 'no API key needed' and 'FREE preview', giving an implied scenario, but provides no explicit when-to-use versus data_session_query or when-not-to-use guidance. The call to 'Try one of sample questions now' actively points toward query-like usage, making routing less clear.

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