Recent news headlines for any company, topic or query: deduplicated titles with source, link and publish date from a broad news index. Window configurable 1-30 days. JSON response. [Paid: $0.01 USDC per call via x402 on Base; the calling client pays automatically.]
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query, company or topic | |
| days | No | Lookback window in days, default 7 |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description compensates well by disclosing the paid nature ($0.01 per call via x402), response format (JSON), deduplication, and configurable window. However, it does not mention rate limits or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences plus a brief pricing note. No redundant information; all content is functional and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description explains the response includes deduplicated titles, source, link, and publish date, which is sufficient for a search tool. No output schema exists, so this level of detail is adequate. Minor gap: no mention of pagination or result limits.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description adds context for the days parameter ('Window configurable 1-30 days') but does not significantly enhance the meaning of the q parameter beyond its schema description. Baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves recent news headlines for any query, with deduplication, source, link, and publish date. This distinguishes it from siblings like web-search (broad web) and job-search (jobs).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions a configurable time window and pricing, but does not explicitly specify when to use this tool versus alternatives like web-search, nor when not to use it. Implicit usage is clear, but no exclusions or alternatives are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.