Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Trace original news sources

news-intelligence_original-source-trace

Cluster similar articles and identify the earliest published item. Later reprints are not treated as independent confirmation. Price $0.05 USDC. POST /api/v1/news-intelligence/original-source-trace. 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_original-source-trace"
  }
}

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 weight and it delivers operational facts an agent needs: price ($0.05 USDC), transport (POST to a named path), and the failure mode (unpaid calls return 402 and do not run). It also discloses the key analytical behavior that reprints are not independent confirmation. It says nothing about output shape, size limits, or whether the input corpus is fetched remotely via rss/url.

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 behavior before pricing and transport details. Every sentence carries information; the endpoint path is arguably redundant with the tool name but is defensible as operational metadata. No filler or hedging.

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, six mutually exclusive ingestion formats, no output schema, and no annotations. The description addresses none of the input-selection problem and gives no sense of what the response contains (clusters? earliest item with URL and timestamp?). For this level of complexity the definition is materially incomplete.

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 (articles, claims, events, file, rss), so the description must compensate and largely does not. The phrase 'cluster similar articles' hints that article records are the primary input, but there is no explanation of the csv/json/text/file/rss ingestion alternatives, what asOf does, or how claims/events interact with articles. An agent cannot tell which input mode to choose from the description.

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 concrete two-part operation: 'Cluster similar articles and identify the earliest published item.' That is a specific verb-plus-resource pair an agent can act on. It does not name or contrast with the closest sibling (news-intelligence_syndication-cluster), so the reader must infer the boundary from the tool name alone.

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 sentence 'Later reprints are not treated as independent confirmation' implies the tool's role in corroboration/verification workflows, which is real usage context. However, there is no explicit when-to-use statement and no named alternative among the many sibling tools, so an agent must infer whether to call this or syndication-cluster first.

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