Skip to main content
Glama

News latest

news_latest
Read-onlyIdempotent

Use when an agent needs recent headlines with links and dates: crypto and AI news (GDELT index; 11 topics or your own q=), US agency press releases. Returns the paid x402 request for your input (GET /news/latest, $0.002 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Headlines with links only. First call each day returns the data itself, free; later calls return the paid request.

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_latest"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoYour own keyword or phrase instead of topic
hoursNoLook-back window in hours
limitNoArticles to return
topicNoTopic (us-agencies and federal-register are US government sources); ignored when q is givencrypto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / topic / description
      Previous value: -"Topic; ignored when q is given"New value: +"Topic (us-agencies and federal-register are US government sources); ignored when q is given"
    • changedInput schema / properties / topic / enum
      Previous value: -[
      -  "crypto",
      -  "bitcoin",
      -  "ethereum",
      -  "solana",
      -  "stablecoin",
      -  "defi",
      -  "regulation",
      -  "ai",
      -  "agents",
      -  "ai-chips",
      -  "payments"
      -]New value: +[
      +  "crypto",
      +  "bitcoin",
      +  "ethereum",
      +  "solana",
      +  "stablecoin",
      +  "defi",
      +  "regulation",
      +  "ai",
      +  "agents",
      +  "ai-chips",
      +  "payments",
      +  "us-agencies",
      +  "federal-register"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnly, idempotent, openWorld, non-destructive); the description adds substantial behavior the annotations cannot express: returns a paid x402 request rather than data, $0.002 per call, bad input refused before charging, and the first call each day being free. It also discloses the return shape ('headlines with links only'), which matters because there is no output schema.

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

Conciseness4/5

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

It is front-loaded with the use case and packed with decision-relevant facts, with no filler. The x402/MPP call-and-cost details make the middle dense, but each clause carries operational meaning.

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

Completeness4/5

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

For a read-only, open-world fetch with no output schema, the description covers the two-step retrieval flow, cost, free-call exception, and return shape — enough to call it correctly. Minor gaps remain (response envelope, error payloads, what 'links' look like), but nothing blocking.

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 the baseline is 3, and the description mostly restates schema content ('11 topics or your own q=', topic ignored when q= is given). It also states '11 topics' while the enum actually contains 13 values, a minor inaccuracy that slightly undermines trust in the parameter narrative.

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 a concrete verb+resource ('recent headlines with links and dates') and scopes it to crypto/AI news via the GDELT index plus US agency press releases, which separates it from siblings like sec_filings or domain_report. It stops short of a crisp one-line summary because the payment mechanics are woven into the same opening sentence.

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

Usage Guidelines4/5

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

'Use when an agent needs recent headlines with links and dates' gives a clear triggering condition, and it explains the q= versus topic= choice. It does not name any sibling alternative or exclusion (e.g., when to prefer sec_filings for filings), so it is clear context without routing guidance.

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