V³ News

v3_global_pulse

Read-onlyIdempotent

Get V³'s Global Pulse — the world's current risk/impact/signal reading and how it has moved over a recent window.

Use when the user asks how tense/volatile the world is right now,
whether global risk is rising or falling, or wants a one-number
situational read rather than a specific event. Scores are 0-100
aggregates across everything V³ tracks (risk = downside pressure,
impact = consequence, signal = momentum, priority = attention
weight).

Args:
    window_days: trailing window for the trend, 2-90 (default 14).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`window_days`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

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

First observedJul 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds meaning of score dimensions (risk, impact, signal, priority) and that scores are 0-100 aggregates, providing behavioral 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?

Two paragraphs: first is purpose and usage, second is parameter details. Front-loaded, every sentence adds value, no wasted words.

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?

Covers purpose, usage, score interpretation, and parameter range. Output schema exists for return values, so not needed in description. Lacks details on trend calculation but adequate for selection.

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

Parameters5/5

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

Although schema has no descriptions, the tool description includes an Args section that fully documents the lone parameter: valid range (2-90) and default (14), adding complete 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?

Description clearly states it gets 'V³'s Global Pulse' with verbs 'get' and specific resource. It contrasts with sibling tools like v3_get_event by stating it provides a 'one-number situational read rather than a specific event', differentiating well.

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?

Explicit usage guidance: 'Use when the user asks how tense/volatile the world is right now... or wants a one-number situational read rather than a specific event.' Clearly tells when to use and when not to.

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

All V³ News tools Inspect

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

Need Help?