Fetch a BBC News live-page text snapshot from one canonical URL, returning current server-rendered updates without broadcast, player, or stream data.
Get a BBC News live-page text snapshot. Returns the current server-rendered text updates from one canonical BBC News live URL. It does not subscribe to updates or return broadcast, player, or stream data.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical BBC News live URL |
Changes observed during successful MCP inspections.
v1.16.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that this is a snapshot (not a subscription) and excludes broadcast/player/stream data, which is useful behavioral context. However, it doesn't mention whether the snapshot is static, how fresh it is, or what happens if the URL is not a live page.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with no wasted words. The core action and return type are front-loaded, and the exclusions are stated compactly. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only tool with no output schema, the description is largely complete. It covers what is returned, what is not returned, and the input requirement. The only minor gap is the lack of detail on URL format/validation, but the schema's 'Canonical BBC News live URL' plus the description's 'live-page' qualifier cover most of the need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter 'url' is described as 'Canonical BBC News live URL'. The description adds the qualifier 'canonical' and 'live' but doesn't provide examples or clarify what makes a URL canonical. Baseline 3 is appropriate since the schema already documents the parameter adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') with a clear resource ('BBC News live-page text snapshot') and explicitly states what it returns ('current server-rendered text updates from one canonical BBC News live URL'). It also distinguishes itself from related tools like bbc_article, bbc_headlines, and cnn_live_story by focusing on live-page text snapshots.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use this tool: when a snapshot of a BBC News live page's text is needed. It explicitly states what it does NOT do ('does not subscribe to updates or return broadcast, player, or stream data'), which helps an agent avoid using it for real-time streaming or media content. However, it doesn't name specific alternative tools for those cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.