Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Cluster syndicated news articles

news-intelligence_syndication-cluster

Group near-duplicate titles and bodies into syndication clusters without counting repeats as confirmation. Price $0.04 USDC. POST /api/v1/news-intelligence/syndication-cluster. 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_syndication-cluster"
  }
}

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 carries the full burden, and it does disclose useful operational facts: the $0.04 USDC price, the POST endpoint, and that unpaid calls return 402 without running. However, it says nothing about what a cluster result contains, how thresholds or grouping heuristics behave, or what happens when near-duplicates span outlets.

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 purpose before the pricing and endpoint logistics. Nothing is padded, though the endpoint and 402 sentences are utility text an agent rarely needs mid-reasoning.

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 10-parameter tool with deeply nested inputs, no annotations, and no output schema, the description does too little: input-mode selection and the shape of returned clusters are both unexplained. The cost/auth behavior is covered, but the calling contract is not.

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?

There are 10 parameters at 0% schema description coverage, including nested objects (articles, claims, events, file, rss), and the description documents none of them. It hints that 'titles and bodies' are the relevant fields but gives no guidance on which input mode to choose or whether the payload sources are mutually exclusive.

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 resource: 'Group near-duplicate titles and bodies into syndication clusters', plus the key semantic caveat 'without counting repeats as confirmation'. That distinguishes it from siblings like claim-source-match and source-independence-analyze, though it never explicitly names an alternative.

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?

Usage is implied rather than stated: the agent can infer this is a pre-step before corroboration counting, but there is no explicit 'use this when...' or 'do not use for...' guidance, and no mention of the sibling tools that also handle source relationships.

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