V³ News

search

Read-onlyIdempotent

Search V³ News for tracked geopolitical events matching a query.

Returns a list of matching events, each with an id (for ``fetch``) and
a v3.news citation url. V³ covers 12 categories (geopolitics, security,
energy, finance, markets, macro, trade, technology, science, climate,
business, public finance) with multi-perspective, cited analysis.

Args:
    query: free-text topic, country, or question (e.g. "Iran sanctions").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes

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.

AddedJul 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds context about categories and return format but does not disclose any behavioral details beyond what annotations imply.

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?

Description is concise, well-structured with purpose, return format, categories, and Args. No wasted words; information is front-loaded.

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?

Given the presence of annotations and output schema, the description provides sufficient context for a search tool. It could mention the relationship with 'fetch' but is otherwise complete.

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?

The Args section in the description adds meaningful guidance for the query parameter (free-text topic, country, or question with example), which is not in the input schema (coverage 0%).

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?

Description clearly states it searches V³ News for tracked geopolitical events and returns a list with id and url. However, it does not differentiate from sibling tool 'v3_search_events' which likely serves a similar purpose.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'v3_search_events' or 'fetch'. There is no mention of prerequisites or exclusions.

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?