Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Detect news claim contradictions

news-intelligence_contradiction-detect

Find affirming vs negating overlapping claims, and label near-duplicate repeats without treating them as confirmation. Price $0.05 USDC. POST /api/v1/news-intelligence/contradiction-detect. 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_contradiction-detect"
  }
}

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
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose genuinely useful behavior: the $0.05 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It stops short of describing what the response contains, whether near-duplicates are flagged in a particular field, or how large inputs are handled.

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 short sentences: purpose first, then cost, then transport and payment failure mode. Nothing is padded, and the most decision-relevant content is front-loaded.

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?

For a tool with ten parameters, deeply nested input objects, no annotations, and no output schema, the definition is thin. It covers purpose and payment gating but omits input selection rules and any description of the returned contradiction/duplicate labels.

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

Parameters1/5

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

Ten top-level parameters, several nested objects, and 0% schema description coverage, yet the description explains none of them. It never says that csv/rss/file/json/text/claims/events/articles are alternative or mutually exclusive input channels, nor what asOf or country do, leaving an agent to guess at input format entirely.

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 uses specific verbs and resources: it finds affirming vs negating overlapping claims and labels near-duplicate repeats. That distinguishes it conceptually from clustering and source-analysis siblings, though it never names an alternative tool.

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?

There is no explicit when-to-use guidance and no stated exclusions or prerequisites for calling it. The phrase 'without treating them as confirmation' clarifies interpretation of results, not when an agent should choose this tool over claim-source-match or syndication-cluster.

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