Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Match claims to sources

news-intelligence_claim-source-match

Match supplied or extracted claims to articles by text overlap. Multiple outlets repeating a claim are not independent confirmation. Price $0.05 USDC. POST /api/v1/news-intelligence/claim-source-match. 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-source-match"
  }
}

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.4/5.0
Behavior4/5

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

With no annotations provided, the description carries real weight and does disclose concrete behavioral facts: cost of $0.05 USDC, the POST endpoint, and that unpaid calls return 402 and do not execute. That is exactly the kind of operational context annotations would normally supply. It stops short of describing matching thresholds, output shape, or limits on volume.

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?

Three short sentences plus endpoint and payment terms, with the core action front-loaded and the cost/402 caveat at the end where a caller needs it. No filler or restated title content.

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 optional parameters, nested objects, no annotations, and no output schema. The description covers purpose, price, and payment failure but leaves an agent unable to know which of the many input modes to use or what the response contains.

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 csv/rss/file/json/text inputs and claims/events/articles arrays, so the description must compensate but barely does. It only implies that claims and articles are the two inputs, saying nothing about the five alternate input carriers, asOf, country, or the nested object fields.

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 both resources: "Match supplied or extracted claims to articles by text overlap." The mechanism (text overlap) is named, which helps distinguish it from semantic verification siblings, but no sibling is named as a contrast so the differentiation is left to inference.

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?

"Supplied or extracted claims" implies the tool accepts either user-provided claims or output from claim-extract, which is useful usage context. However there is no explicit when-to-use vs. when-not, and no pointer to alternatives such as source-independence-analyze despite the description raising an independence caveat.

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