Skip to main content
Glama
Sign In

Orb Studio news radars

by io.github.farenberglord-star
OverviewDiscussionsAdmin

World radio as text: how international broadcasters cover a story

get_world_voices
Read-only

Latest headlines of 16 international broadcasters (BBC, DW, France 24, RFI, Euronews, NPR, CBC, ABC Australia, CNA, Al Jazeera, CGTN, SCMP, NDTV, Africanews, Times of Israel, Meduza) with country and ownership (public, state-funded, state, private, independent). Without arguments: today's topics covered by 3+ stations — who said what and who is silent — plus an editor's comparison of framing. With topic: every station's latest headline containing that word (e.g. Iran, Frankfurt, Gaza) and which stations are silent. Compare framing, not truth.

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": "get_world_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOptional keyword, English works best: Iran, Ukraine, Frankfurt…
stationNoOptional station id: bbc, dw, france24, rfi, euronews, npr, cbc, abc_au, cna, aljazeera, cgtn, scmp, ndtv, africanews, times_israel, meduza

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real disclosure burden and does it well: it explains the default aggregation threshold (3+ stations), the 'who is silent' reporting, and the editorial framing comparison. It does not state freshness/latency, rate limits, or result size, and it never mentions the station filter's effect on behavior.

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 resource and scope, and the mode branching is easy to scan. The 16-name enumeration plus ownership taxonomy consumes significant space, but it does communicate coverage scope rather than being filler.

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

Completeness4/5

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

For a 2-parameter read tool with no output schema, the description covers the argument-driven behaviors well enough to call correctly. The gap is the undocumented `station` parameter and no hint about output shape (headline format, per-station grouping), which the absent output schema leaves to the description.

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 coverage is 100%, so both parameters are already documented, making 3 the baseline. The description reinforces the topic behavior (per-station matches plus silence detection) but ignores the `station` parameter entirely, leaving one of the two inputs without any narrative semantics.

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?

Names a specific resource (latest headlines from 16 named international broadcasters) plus what it enriches them with (country and ownership classification). The two operating modes are stated concretely, so an agent knows exactly what it gets back and can distinguish it from every sibling tool listed.

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

Usage Guidelines4/5

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

Explicitly branches behavior by arguments: 'Without arguments: today's topics covered by 3+ stations' vs 'With topic: every station's latest headline containing that word', and adds the framing caveat 'Compare framing, not truth.' What's missing is any statement of alternatives or exclusions, though no sibling covers this domain.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Orb Studio news radars toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources