Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Build news verification evidence report

news-intelligence_verification-evidence-report

Aggregate source tracing, syndication, claims, contradictions, corrections, and independence findings. Repeats are never independent confirmation. Price $0.08 USDC. POST /api/v1/news-intelligence/verification-evidence-report. 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_verification-evidence-report"
  }
}

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

B3.1/5.0
Behavior3/5

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

With no annotations, the description does carry real behavioral weight: it discloses the price ($0.08 USDC), the POST endpoint, and that unpaid calls return 402 without executing — genuinely useful pre-call context. It also flags the key interpretation rule that repeated syndication never counts as independent confirmation. However, it says nothing about side effects, processing latency for large article/claim payloads, or what the report contains, and there is no output schema to fill that gap.

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?

Three tight sentences with the capability statement front-loaded, followed by the methodological caveat and then the commercial/transport facts. Nothing is padded, though the price, endpoint, and 402 notes are somewhat compressed together and could be grouped more cleanly.

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?

This is a high-complexity tool — 10 parameters, nested objects, no annotations, no output schema — and the description covers none of the input contract and little of the output shape. The payment and 402 behavior are covered, but an agent could not reliably construct a valid call from this definition alone.

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 for articles, claims, events, rss, and file, plus csv/json/text/asOf/country — and the description explains none of them. An agent gets no hint about which input form to supply, whether inputs combine, or that the tool will accept a single article set, a claim list, or a raw file. The enumerated finding types loosely suggest what data is expected but supply no field-level meaning.

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?

Specific verb plus resource: 'Aggregate source tracing, syndication, claims, contradictions, corrections, and independence findings' names exactly what goes in and that the tool is a rollup. It is distinguishable from the individual sibling analyzers (original-source-trace, syndication-cluster, contradiction-detect, etc.) because it consumes their outputs. It stops short of explicitly framing itself as the one-shot alternative to calling those siblings separately.

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?

The aggregation framing implies the use case — get all verification findings in one call rather than running each detector — but the description never states when to prefer this over the sibling tools or what prerequisites the input must satisfy. 'Repeats are never independent confirmation' is a methodological rule about results, not guidance on invocation. Usage is inferable but unstated.

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