Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Analyze news source independence

news-intelligence_source-independence-analyze

Count distinct outlets and mark syndicated/similar copies as non-independent. Repeats are never claimed as confirmation. Price $0.04 USDC. POST /api/v1/news-intelligence/source-independence-analyze. 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_source-independence-analyze"
  }
}

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, the description carries the full behavioral burden. It usefully discloses pricing, the POST endpoint, the 402 behavior for unpaid calls, and the key rule that repeats are never treated as confirmation. However, it does not explain what inputs are required or what happens when no content is supplied, and it gives no output behavior.

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?

The description is short and front-loaded with the core behavior. The operational details about price, endpoint, and unpaid-call behavior are compact and each sentence contributes useful information.

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 complex tool with 10 optional input parameters, nested objects, no annotations, and no output schema, the description is too sparse. It covers payment and core logic but does not explain accepted input combinations, expected inputs, or what the result contains.

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?

The schema has 10 parameters with 0% description coverage, and the description does not mention any parameter by name. It does not explain how text, csv, json, file, rss, articles, claims, events, country, or asOf differ or interact, leaving every input option undocumented beyond the raw schema.

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 states specific actions: count distinct outlets and mark syndicated/similar copies as non-independent. It is clear what the tool does, though it does not explicitly distinguish itself from sibling tools like syndication-cluster or original-source-trace.

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 guidance on when to use this tool versus related siblings such as syndication-cluster or original-source-trace. The purpose implies a use case, but no conditions, exclusions, or alternatives are named.

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