Skip to main content
Glama

V³ News

by news.v3

v3_breaking_now

Read-onlyIdempotent

Get events V³ is currently tracking in BREAKING tempo — fast- moving stories under near-real-time monitoring right now.

Use when the user asks "what's breaking", "any breaking news", or about a developing situation. Returns an empty list when nothing is in breaking tempo (a quiet news moment), which is itself a signal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already provide readOnly, idempotent, non-destructive hints. Description adds the specific behavior of returning empty list when nothing is breaking, which is valuable context beyond annotations.

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

Conciseness5/5

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

Three sentences, each with a purpose: first states function, second gives usage guidance, third describes edge case. No wasted words, front-loaded.

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?

Given zero parameters, presence of output schema, and clear annotations, the description fully covers purpose, usage, and expected behavior. No gaps.

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

Parameters4/5

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

No parameters in schema, so description does not need to add param info. Baseline 4 for 0 parameters is appropriate.

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?

Description states specific action: 'Get events V³ is currently tracking in BREAKING tempo'. Verb+resource clearly defined. Distinguishes from siblings like v3_latest_brief by emphasizing 'near-real-time monitoring'.

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?

Explicitly tells when to use: 'Use when the user asks "what's breaking", "any breaking news", or about a developing situation.' Also describes the empty list case, which is a signal.

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

All V³ News toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

The tool set contains two overlapping search tools ('search' and 'v3_search_events') and two overlapping fetch tools ('fetch' and 'v3_get_event'), making it unclear which one an agent should call. The differences are not obvious from the names/descriptions alone, creating real selection ambiguity.

Naming Consistency2/5

Naming is inconsistent: 'fetch' and 'search' are bare single verbs while the rest use a 'v3_' prefix with varied noun/verb forms like 'v3_breaking_now' and 'v3_global_pulse'. The pattern is not predictable enough for an agent to infer tool names.

Tool Count4/5

Seven tools is a reasonable size for a news/intelligence server. However, at least two pairs are redundant, so the count feels slightly padded rather than tightly scoped.

Completeness4/5

The core workflow of searching/fetching events, checking breaking news, and getting a global pulse/brief is covered. Minor gaps exist, such as no explicit category listing tool or way to compare multiple events side by side, but agents can work around these.

Resources