Skip to main content
Glama

ScienceNews Magazine Articles — buy per-query in-session (scinewsmag)

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: scinewsmag: Science News Magazine Articles. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What are the latest Science News articles?; Summarize recent paleontology stories.. 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

A3.5/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld=false, yet the description adds genuinely non-structured context: no API key required, no payment for the preview, and a rate limit of max 20 queries/session. The "Price 0.01 USDC/query" line describes the underlying listing rather than this call, which is mildly ambiguous but clarified by the immediately following "FREE preview — no key, no payment." Useful behavioral disclosure beyond the annotation layer.

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?

It is short and front-loads the listing name and pricing, but "No API key needed" and "no key, no payment" are redundant, and the closing call-to-action ("Try one of the sample questions now") is promotional filler rather than functional information. The sample questions are the only sentences that add semantic value.

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 rich annotations and 100% schema coverage the basics are covered, but there is no output schema, so the description carries the burden of explaining what a preview returns — that it is public metadata only is stated solely in the schema description, not here. It also omits the natural next step (opening a paid session) that an agent would need after previewing.

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 slug and question are already explained in the schema, including the default-slug routing behavior and that question is echoed back. The description's sample questions do illustrate the shape of the question parameter, but add no syntax, length, or default details 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete resource being previewed ("scinewsmag: Science News Magazine Articles") and marks it as a "FREE preview," so an agent can tell this is a zero-cost look at a paid listing. It never names or contrasts itself with the paid path (data_session_open/data_session_query), so differentiation is left implicit. Clear but not sibling-aware.

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?

Usage is only implied: "Try one of the sample questions now" plus two sample questions suggests this is a trial call before paying for a full session. Nothing states when to prefer this over data_session_query or discover_agents, and there are no exclusions or prerequisites beyond "no key, no payment." Adequate but the routing decision is left to inference.

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