Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Extract news claims

news-intelligence_claim-extract

Extract claim-like sentences and quotes from supplied article text using local heuristics. Price $0.04 USDC. POST /api/v1/news-intelligence/claim-extract. Unpaid calls return 402 and do not run.

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-intelligence_claim-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
rssNo
asOfNo
fileNo
jsonNo
textNo
claimsNo
eventsNo
countryNo
articlesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses price, endpoint, and that unpaid calls return 402 without executing, and notes the heuristic nature — but says nothing about output shape, determinism/quality of heuristic extraction, auth mechanics, rate limits, or whether input payloads are stored.

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?

Four short sentences, front-loaded with the core action, with payment and error semantics compactly appended. Little waste, though the endpoint path and price sit in the description rather than being strictly necessary for tool selection.

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

Completeness2/5

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

A 10-parameter tool with nested objects, no annotations, and no output schema. The description leaves the multi-source input contract and the return value almost entirely unexplained, which is a substantial gap for an agent trying to construct a valid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 parameters including nested objects, and the description only vaguely references 'article text'. It does not explain the several distinct input channels (csv, rss + limit, file with mediaType, json, articles, claims, events), the meaning of asOf, or how country filters extraction.

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?

States a specific verb and resource ('Extract claim-like sentences and quotes'), plus the mechanism ('local heuristics') and scope ('supplied article text'). It does not differentiate from siblings such as claim-source-match or contradiction-detect, which operate on related claim data.

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?

No indication of when to call this versus the sibling claim/source tools, and no guidance on which of the many input modes (text, articles, csv, rss, file, json, claims, events) is appropriate for a given situation. The agent must infer usage entirely.

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