V³ News

v3_search_events

Read-onlyIdempotent

Search V³ News for tracked geopolitical events.

Use when the user asks what is happening on a topic, in a country,
or in a domain (e.g. security, energy, finance, technology). Returns
a ranked list of events with why-it-matters, risk/impact/signal
scores, and a v3.news link for each.

Args:
    query: free-text topic (e.g. "Iran sanctions", "Taiwan"). Optional.
    country: ISO-3166 alpha-2 code to filter by (e.g. "US", "CN"). Optional.
    category: V³ category slug — one of geopolitics, security_risk,
        energy_resources, finance, markets, macroeconomics,
        public_finance, trade_supply, technology, science_biosecurity,
        environment_climate, business. Optional.
    limit: max results, 1-20 (default 10).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`country`	No
`category`	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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds value by detailing the output structure (why-it-matters, scores, link) and parameter constraints (limit 1-20). No contradiction with 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?

Concise and well-structured: purpose, usage guidance, output description, then parameter list. Each sentence is necessary and no filler.

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 4 optional parameters and an output schema, the description covers all needed context: usage scenarios, parameter details, and output format. No gaps.

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?

Schema descriptions are absent (0% coverage), but the description fully compensates: provides purpose, examples, and constraints for each parameter (query, country, category list, limit range). Adds meaning beyond schema.

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?

The description clearly states it searches for tracked geopolitical events in V³ News, specifying verb and resource. It distinguishes from siblings like v3_get_event (single event) and v3_latest_brief (different scope) by focusing on search and ranking.

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

Usage Guidelines4/5

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

Explicitly says when to use it: when user asks about a topic, country, or domain. Provides examples. However, it doesn't explicitly mention alternatives or when not to use it (e.g., for single event lookup, v3_get_event would be better).

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?