Skip to main content
Glama

BRAINIAC News Verification & Information Intelligence

Build news event timeline

news-intelligence_event-timeline-build

Order supplied events or dated articles into a timeline without inventing missing dates. Price $0.04 USDC. POST /api/v1/news-intelligence/event-timeline-build. 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_event-timeline-build"
  }
}

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 real work: it discloses cost ($0.04 USDC), the failure mode (402 and no run on unpaid calls), and a core behavioral guarantee against inventing dates. However, it omits ordering direction, what happens to undated items, and any hint of the response shape, which matter for a tool with this much input flexibility.

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, front-loaded sentences with the operation stated first and no filler. The endpoint path largely restates the tool name, but the pricing and 402 note earn their space.

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 nested objects, no annotations, and no output schema, the description covers calling mechanics and one quality guarantee but leaves input selection and return behavior unspecified. An agent would not know how to choose between the many input channels from the description alone.

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, so the description carries the full burden and mostly doesn't. It gestures at the 'events' and 'articles' inputs but says nothing about csv, rss, file, json, text, claims, country, or asOf, leaving the majority of inputs undocumented in both places.

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?

Names a specific verb and output artifact: 'Order supplied events or dated articles into a timeline,' plus the constraint 'without inventing missing dates.' That is enough to distinguish it from claim extraction or contradiction detection siblings, though no sibling is named explicitly.

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 by naming the accepted inputs ('supplied events or dated articles') and one hard rule about not fabricating dates. There is no explicit when-to-use versus an alternative tool, and no stated prerequisites beyond payment.

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