Skip to main content
Glama

Latest anchor broadcast

get_broadcast
Read-only

Current Orb Studio broadcast: top headlines across all radars with short anchor lines in Russian, German or English, written by Claude from the headlines, plus track_of_the_day — the newest Orb Studio song made from the radars (title, style, mood, lyrics excerpt, listen link; full lyrics via get_tracks) violin_of_the_day — today's violin piece composed from the sensors (full score via get_violin) on_air_now — official live events happening now and the next one (text after the event via get_live), and picture_now — the painter's current picture of a city by the sea drawn from the radars (PNG link; full mapping and the image via get_canvas).

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_broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of anchor lines (default en)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely non-obvious context: the content is written by Claude from the headlines and the items are daily-rotating (today's song, today's violin, current picture). It omits refresh cadence, payload size, and whether a broadcast always exists — relevant for an open-world aggregator with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is a single run-on sentence with no delimiters between the five returned components; the embedded parentheticals about alternate tools blur the boundaries further. It is information-dense but poorly front-loaded and hard to scan — a bulleted or semicolon-separated list would cost no extra length.

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?

With no output schema, the description carries the burden of explaining return values, and it does so for every component, including what each sub-item contains (title/style/mood/lyrics excerpt, PNG link) and where to get the fuller version. Only freshness/pagination and error behavior for a nonexistent broadcast are unaddressed.

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% and the enum with its 'default en' note already documents lang fully. The description reinforces that the language choice applies to anchor lines specifically, which is a small clarification of scope, but nothing about behavior for lang is added beyond that. Baseline 3 applies.

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 names the resource (the current Orb Studio broadcast) and enumerates its constituent parts — headlines, track_of_the_day, violin_of_the_day, on_air_now, picture_now — so an agent knows exactly what comes back. It is distinguishable from siblings like get_tracks and get_canvas, which it explicitly defers to. It stops short of 5 only because the framing is a dense noun pile rather than a clear verb+object statement.

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 'current'/'today' framing and by pointing to get_tracks, get_violin, get_live and get_canvas for full content, which tells an agent this is a summary/index entry point. However, there is no explicit statement of when to prefer this over get_radars, get_world_voices or ask_david, and no exclusions or prerequisites.

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.