Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_ai_news-brief

[x402 paid: $0.002 USDC on Base] Live news brief on any topic: fresh Google News headlines fetched at call time + LLM summary (5 bullets). News API + summarizer replaced by one payment. tools/call returns the live payment challenge.

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": "tool_ai_news-brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoexample: base chain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses the price ($0.002 USDC on Base), the x402 payment protocol, that headlines are fetched at call time (freshness guarantee), and the output shape of five bullets. Most importantly it warns that tools/call returns a payment challenge rather than results, which would otherwise confuse an agent. It stops short of covering failure modes, retry/payment-flow steps, or rate limits.

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?

One dense but front-loaded sentence with the price prefix first, followed by two short clarifying sentences about payment substitution and the challenge response. Nothing is wasted; even the price tag is operationally relevant to an agent deciding whether to call it.

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 one-parameter, paid tool with no output schema, the description covers what an agent needs: cost, payment mechanism, data freshness, and result format. The main remaining gap is the payment-challenge resolution path — what to do after receiving the challenge — which leaves the actual call sequence underspecified.

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% and the single 'topic' parameter is documented with an example, so the schema already does the work. The description adds only the 'any topic' framing, confirming the parameter is free-form rather than an enum, which is a marginal but real addition.

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 specific verb and resource: it returns a live news brief on any topic, combining freshly fetched Google News headlines with an LLM five-bullet summary. That is precise enough to distinguish it from a generic chat or summarize tool, though it never explicitly contrasts itself with the closest sibling, tool_crypto_news.

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 implied rather than stated: 'any topic' signals a general-purpose news lookup versus the crypto-specific siblings, and the payment note signals this is a paid endpoint. There is no explicit when-to-use/when-not-to-use guidance or named alternative for users who do not want to pay.

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