Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

news

[$0.001] Fetch real-time breaking news headlines and articles by topic or keyword with automated sentiment polarity and extracted named entities in structured JSON.

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": "news"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch query to filter news results
limitNoMax results to return (default 50, max 500)
topicNoTopic or keyword (a category name or free text)
fieldsNoReturn only these result keys, e.g. ["title","url","sentiment"]
categoryNoNews category (see enum; full list free at /pricing and /api/news/check)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the $0.001 cost, that results are real-time, and that output is structured JSON with sentiment and entities — but says nothing about pagination, freshness window, snippet vs full article text, or whether the enrichment is always included.

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?

A single dense sentence with the price front-loaded and no wasted words. Everything stated earns its place.

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?

Five optional parameters with no output schema and no annotations; the description partly compensates by naming the return shape (JSON with sentiment and named entities). It still leaves the q-vs-topic relationship, result volume behavior, and output field structure for the agent to infer.

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 q, limit, topic, fields, and category. The description's 'by topic or keyword' loosely maps to q/topic but does not clarify their overlap (both are free-text filters), and adds no meaning beyond the schema.

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 states a specific verb and resource — 'Fetch real-time breaking news headlines and articles' — and adds the enrichment (sentiment polarity, named entities, structured JSON). It never distinguishes this general news tool from siblings like crypto_news or topic_briefing, so the agent must guess which news endpoint is appropriate.

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?

'by topic or keyword' hints at the input mode but gives no when-to-use conditions, no exclusions, and no named alternative. With crypto_news and topic_briefing in the sibling set, the absence of any routing guidance is a real gap.

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