A
license-
qualityC
maintenanceReal-time news events, clustered by AI from hundreds of sources, classified by topic and geography, ranked by importance.
53
MIT
V³ News
by news.v3
Server Details
Cited geopolitical events, multi-perspective briefs, and live breaking news from V³ News.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4.5/5 across 7 of 7 tools scored. Lowest: 3.5/5.
Server CoherenceA
Disambiguation3/5
There is functional overlap between search and v3_search_events (both search events) and between fetch and v3_get_event (both retrieve event details), which could confuse an agent despite minor differences in output. The other three tools are distinct.
Naming Consistency2/5
Naming is inconsistent: some tools (fetch, search) lack a prefix while others use the 'v3_' prefix. Verbs also vary (fetch, search, get, etc.), and there is no clear pattern.
Tool Count5/5
7 tools is well-scoped for a geopolitical news server, covering search, detail retrieval, breaking news, global pulse, and daily brief without unnecessary bloat.
Completeness4/5
The tool set covers core operations (search, get, breaking, overview), but there is redundancy between search/fetch pairs. Missing features like category listing or trend analytics are minor gaps.
Available Tools
7 toolsfetchARead-onlyIdempotentInspect
Fetch the full text of a single V³ event by id (from search).
Returns V³'s public summary (headline, why-it-matters, risk/impact/
signal scores, coverage depth) plus the canonical v3.news url for
citation. The full country-by-country perspectives, timeline, decisions
and calibrated outcomes live at that url.
Args:
id: the V³ event id returned by ``search``.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by detailing what the tool returns (summary, scores, URL) and clarifies that full details are at the URL, going beyond the 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?
The description is concise with three sentences: core purpose, output contents, and parameter explanation. No unnecessary words, well-structured for quick parsing.
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?
For a single-parameter tool with an output schema, the description is complete. It covers what is returned and where to find the full content, providing sufficient context for the agent.
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 coverage is 0% for the 'id' parameter, but the description fully compensates by explaining that the id is 'the V³ event id returned by search', defining the source and type precisely.
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 the verb 'Fetch' and the resource 'full text of a single V³ event by id', specifying that the id comes from 'search'. This distinguishes it from sibling tools like 'search' and 'v3_get_event'.
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 mentions that the id comes from 'search', providing clear context for when to use this tool. However, no explicit exclusions or alternatives are given, but the usage is clear from the context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchARead-onlyIdempotentInspect
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").
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
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.
v3_breaking_nowARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
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.
v3_get_eventARead-onlyIdempotentInspect
Get a single V³ event: headline, why-it-matters, scores, and how much structured analysis V³ holds on it (perspectives, decisions, outcomes).
Use after v3_search_events (or v3_breaking_now) when the user wants
detail on a specific event. This returns V³'s public summary; the
full country-by-country perspectives, timeline, decisions to watch,
and calibrated outcomes are on v3.news at the returned url (a V³
account unlocks the multi-perspective analysis).
Args:
event_id: the V³ event id from a prior tool result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| event_id | Yes |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.8/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds context that it returns a public summary and that a V³ account unlocks full multi-perspective analysis, plus mention of returned URL. No contradictions; description adds value 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 well-structured paragraphs: first defines return fields, second gives usage context and parameter. No extraneous text; every sentence adds value. Front-loaded with purpose.
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?
With output schema present, description doesn't need to detail return values, but it still summarizes key fields. Parameter explanation is adequate. Sibling tools are mentioned. For a single-resource retrieval tool, this is fully complete.
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 has one parameter (event_id) with no description (0% coverage). Description specifies it is 'the V³ event id from a prior tool result,' adding essential context about provenance and format.
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?
Clearly states it retrieves a single V³ event with specific fields (headline, why-it-matters, scores, etc.). Differentiates from siblings by indicating usage after v3_search_events or v3_breaking_now.
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 says 'Use after v3_search_events (or v3_breaking_now) when the user wants detail on a specific event.' Also contrasts with full analysis on v3.news, providing clear when-to-use and exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
v3_global_pulseARead-onlyIdempotentInspect
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).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| window_days | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
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.
v3_latest_briefARead-onlyIdempotentInspect
Get V³'s latest global intelligence brief — the chief-of-staff top line on what matters in the world right now, with per-category state and counts.
Use when the user asks for a world summary, "what's happening today", or a geopolitical situation overview.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, indicating safe, non-destructive behavior. The description adds context that the brief is a 'chief-of-staff top line' with 'per-category state and counts', which enhances understanding of the output content without contradicting 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?
The description is extremely concise: two clear, front-loaded sentences. The first defines the tool's purpose and content, the second provides usage scenarios. No wasted words; every sentence earns its place.
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 no parameters, rich annotations, and an output schema (which covers return format), the description provides sufficient context: it names the tool's output ('global intelligence brief', 'per-category state and counts') and usage cases. No gaps remain.
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?
With zero parameters and 100% schema coverage (vacuously), the description naturally adds no parameter info. According to guidelines, baseline is 4 for 0 parameters. The description does not need to elaborate on parameters, so score is 4.
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 the tool retrieves 'V³'s latest global intelligence brief' with 'per-category state and counts'. It uses specific verb 'Get' and resource 'global intelligence brief', distinguishing it from sibling tools like v3_breaking_now or v3_global_pulse which have different scopes.
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?
The description explicitly says to use it when the user asks for a 'world summary', 'what's happening today', or 'geopolitical situation overview'. While it doesn't explicitly mention when not to use or contrast with siblings, the use cases are clear and cover typical scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
v3_search_eventsARead-onlyIdempotentInspect
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).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| country | No | ||
| category | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityAmaintenanceRead-only, source-linked news intelligence for AI agents: search The Neural Ledger's stories, retrieve story details with citations and revision history, and resolve related entities and assets. It is an evidence layer, not a trading or execution service.82MIT
- AlicenseAqualityDmaintenanceProvides AI agents with global tech news from 500+ sources across regions, with translated titles, scoring, and clustering tools for real-time intelligence.852MIT
- Alicense-qualityBmaintenanceProvides current headlines from 17 news outlets across the political spectrum with bias tags and blindspot detection for stories covered by only one side.MIT