A
licenseNot graded
qualityC
maintenanceReal-time news events, clustered by AI from hundreds of sources, classified by topic and geography, ranked by importance.
42
MIT
V³ News
by news.v3
Server Details
Cited geopolitical events, multi-perspective briefs, and live breaking news from V³ News.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
7 toolsfetchARead-onlyIdempotentInspect
Fetch the full text of a single V³ event by id (from search).
Returns V³'s public report (headline, why-it-matters, the full
long-form report when V³ has authored one, risk/impact/signal scores,
coverage depth) plus the canonical v3.news url for citation. The
country-by-country perspectives, timeline, decisions and assessed
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 | ||
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful context by describing what the report contains, noting that the long-form report is included only 'when V³ has authored one', and directing further details to the canonical URL. This goes beyond annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately sized, with the main purpose front-loaded and a concise list of return components. It avoids unnecessary filler and directly communicates the essential information. Minor improvement could be splitting the return list for scannability, but it is already clear and efficient.
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?
For a simple one-parameter read tool with a rich output schema, the description covers the return content, the id source, and points to where additional data lives. It does not mention error scenarios or URL format, but these are not critical for a read-only fetch tool. The context is complete enough for correct selection and invocation.
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 schema only defines 'id' as a required string with no description, so the description carries the burden. It explains that the id is the V³ event id returned by 'search', which is exactly the semantic detail an agent needs. For a single parameter with 0% schema coverage, this is sufficient.
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?
The description states a specific verb (Fetch) and resource ('full text of a single V³ event by id'), and clearly identifies the id source as 'from search'. It details the return payload, which helps an agent understand what the tool produces. However, it does not explicitly distinguish itself from sibling v3_get_event or other v3_* tools, though the reference to search narrows the context.
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 an id returned by 'search', which provides clear guidance on the prerequisite call. It implies this tool is for retrieving a specific event's full report, but it does not enumerate when to use alternatives like v3_get_event or v3_search_events. The context is clear and actionable, but lacks explicit exclusions.
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 | ||
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.
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 | ||
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.
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 assessed 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 | ||
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond the readOnly/openWorld/idempotent annotations: it returns only V³'s public summary, the full country-by-country analysis lives at the returned url, and a V³ account unlocks the multi-perspective analysis. This helps the agent set correct expectations about depth and access limitations.
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 well-structured and front-loaded, opening with the core action and payload, then usage context, then access limitations, then the argument note. Each sentence serves a purpose and the length is appropriate for the tool's complexity.
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 an output schema present, the description does not need to document return fields. It covers the tool's purpose, when to use it, how to get the id, and what the output represents, making it complete for an agent to select and invoke correctly.
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 schema provides only a plain 'event_id' string with a 0% description coverage, so the description must compensate. It does: 'the V³ event id from a prior tool result' tells the agent exactly where to source the value, though it does not specify format or validation rules.
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 states a specific verb and resource: 'Get a single V³ event' with a concrete list of contained fields (headline, why-it-matters, scores, perspectives, decisions, outcomes). It clearly differentiates itself from v3_search_events by framing this as the detail-retrieval step that follows search.
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 guidance is given: use after v3_search_events or v3_breaking_now when the user wants detail on a specific event. This tells the agent exactly when to invoke this tool rather than its siblings.
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 | ||
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.
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 | ||
TDQS
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 | ||
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Added
fetch - Added
search
5 tool updates
- First observed
v3_breaking_now - First observed
v3_get_event - First observed
v3_global_pulse - First observed
v3_latest_brief - First observed
v3_search_events
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Live world news deduplicated into story events, with corroboration counts and source links.
51Live geopolitical and markets intelligence wire: 35k+ wire items, event threads, 55k+ articles.
Read-only live geopolitical-risk sensing for agents. ARCANE notices; never forecasts or advises.
Free cross-lingual news briefings for AI agents across 89 languages. Read-only, hosted.
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
- AlicenseNot gradedqualityBmaintenanceProvides current headlines from 17 news outlets across the political spectrum with bias tags and blindspot detection for stories covered by only one side.1MIT
Try in Browser
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.