Skip to main content
Glama

News research briefing

blackwood_news_briefing
Read-only

Use when you need a news briefing, a research summary of recent coverage or an analysis of what the press says about a topic or company. Do not use for breaking news, paywalled pages or one known article (use blackwood_webpage_markdown). Returns JSON with a research briefing on a topic in one call: up to 3 recent GDELT news articles, each read and summarized, with source and link, below the price of separate calls for 0.04 USDC per call. Typical response time 15000 ms (p95). Category: Search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "blackwood_news_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back to look for news, in hours, 1 to 72 (24 when omitted), e.g. 48
topicYesTopic, company or person to research, e.g. stablecoin regulation
languageNoLanguage of the summaries (English when omitted), e.g. Portuguese
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already carry the safety profile (readOnly, openWorld, non-idempotent, non-destructive), and the description adds genuinely useful behavior beyond them: the 0.04 USDC per-call cost, the ~15000 ms p95 latency, and the shape of the result (up to 3 articles, each read and summarized, with source and link). Cost and latency are exactly the signals annotations cannot convey.

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?

Front-loaded with the 'Use when...' trigger and tightly packed with no filler sentences. It is a dense single paragraph that mixes usage, exclusions, output, cost and latency, which slightly hurts scannability, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is optional, yet the description still summarizes the response. Combined with clear usage, exclusions, cost and latency, nothing material is missing for an agent deciding to call it; the only mild gap is that the very close sibling blackwood_news_search is not explicitly differentiated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters (topic, hours, language, response_format) are already documented in the schema. The description adds nothing parameter-specific beyond mentioning articles, so the baseline 3 for fully covered schemas applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: a news briefing / research summary built from up to 3 recent GDELT articles that are read and summarized. It also explicitly distinguishes itself from a sibling by routing single-article lookups to blackwood_webpage_markdown, so an agent can separate it from that alternative without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('news briefing, research summary of recent coverage, analysis of what the press says') and when-not ('breaking news, paywalled pages, one known article'), and names the alternative tool for the excluded case. This is close to textbook routing guidance.

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