Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Detect news correction history

news-intelligence_correction-history-detect

Flag correction, update, and retraction wording or updatedAt changes in supplied articles. Price $0.03 USDC. POST /api/v1/news-intelligence/correction-history-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_correction-history-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.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose genuinely useful operational facts: the $0.03 USDC price, the POST endpoint, and that unpaid calls return 402 and do not execute. It says nothing about the shape of the returned flags, whether detection is deterministic, rate limits, or idempotency, so the behavioral picture remains partial.

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, front-loaded with the detection purpose, followed by the commercial and transport details. Every sentence carries information; only the redundancy between the endpoint path and the tool name is mildly wasteful.

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 10 parameters, nested objects, no output schema, and no annotations, this description is thin. An agent still cannot tell which input modality to use, what asOf does, or what a detection result looks like, so it is not complete enough to call correctly without guesswork.

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, and file, and the description adds essentially no parameter meaning. It never explains that content can arrive via text, csv, json, file, rss, or a structured articles array, nor what asOf controls, which is a serious gap given zero required parameters and multiple mutually substitutable input channels.

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 opens with a specific verb and resource: 'Flag correction, update, and retraction wording or updatedAt changes in supplied articles.' That is concrete enough for an agent to know exactly what the tool detects. It does not, however, distinguish itself from close siblings such as contradiction-detect or original-source-trace, so it falls short of a 5.

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, no exclusion criteria, and no named alternative. The phrase 'in supplied articles' only weakly implies the input context; an agent has no basis for choosing this over contradiction-detect or syndication-cluster when both seem plausible.

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