NewsMCP

check_limits

Report what this caller may do right now — and never spend any of it to find out.

Answers the questions the news tool descriptions cannot: how many searches are left this hour, how far back this plan reaches, the largest limit it allows, how many searches may run at once, and how long to wait if the budget is spent. These ceilings are per-plan and change without a release, so trust this over any number written into a description.

Checking is free: the endpoint is exempt from every metering stage, so calling it does not consume an hourly call, a concurrency slot, or a credit.

Reach for it before planning a batch of calls, and after any plan-limit or rate-limit error instead of guessing the ceiling that was hit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`api_key`	No	Optional NewsMCP API key. Report the ceilings for this key's plan; omit to report the keyless ceilings.
`response_format`	No	`text` (default) for a readable summary, `json` for the raw payload.	text

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description fully carries behavioral disclosure. It explicitly states the call is free: 'the endpoint is exempt from every metering stage, so calling it does not consume an hourly call, a concurrency slot, or a credit.' It also discloses that limits are per-plan and change without a release, preventing the agent from trusting stale values.

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

Conciseness5/5

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

Three tight paragraphs with a front-loaded definition, followed by concrete details and usage timing. Every sentence adds value: the free-check behavior, the dynamic nature of limits, and the pre/post-error usage guidance. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (zero required params), has full schema coverage, and an output schema exists so return values need not be described. The description covers purpose, usage timing, and the key behavioral trait (free to call), making it complete for agent 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 description coverage is 100%, so the schema already documents both parameters. The description adds broader context about per-plan limits but does not need to compensate for missing parameter documentation. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description opens with a clear verb and resource: 'Report what this caller may do right now.' It then enumerates exactly what the tool answers (searches left, plan horizon, largest limit, concurrency, wait time), making its purpose unmistakable and distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'Reach for it before planning a batch of calls, and after any plan-limit or rate-limit error instead of guessing the ceiling that was hit.' It also positions the tool as authoritative over numbers in other descriptions, telling the agent to prefer it.

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

All NewsMCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Each tool has a clear primary role: news searches digests, get_story expands one story, check_coverage verifies claim independence, check_limits reports quotas, and check_health tests API connectivity. The only mild overlap is that news can fetch by id while get_story also expands a story, but their descriptions make the distinction clear.

Naming Consistency3/5

Three tools use a consistent check_ prefix, and get_story follows a verb_noun pattern, but the primary search tool is simply named news, which breaks the convention. The naming is readable and all lowercase snake_case, but the mix of check_, get_, and a bare noun is not fully consistent.

Tool Count5/5

Five tools is well-scoped for a news-focused MCP server: search, detail expansion, coverage verification, usage limits, and health checking each earn their place. There is no bloat or obvious redundancy.

Completeness5/5

The tool surface covers the full intended workflow: search synthesized news, expand a story to full details, verify claim coverage, check live plan limits, and diagnose connectivity. Users can discover stories, dive deeper, and understand constraints without hitting dead ends.

Resources

Need Help?