Skip to main content
Glama

pulsenetwork

by com.theaslangroupllc.pulse

geopoliticalpulse

GeopoliticalPulse: Real-time geopolitical intelligence for investors, compliance teams, and AI agents. Political risk, conflict monitoring, sanctions, elections, trade tensions, and regional situational awareness for 19

Coverage: Global

Endpoints: • country-risk ($0.15): Country Risk Assessment • conflict-scan ($0.20): Conflict Scan • sanctions-intel ($0.15): Sanctions Intelligence • election-watch ($0.15): Election Watch • trade-tension ($0.20): Trade Tension Analyzer • regime-brief ($0.20): Regime Brief • event-impact ($0.25): Geopolitical Event Impact • instability-signal ($0.20): Instability Early Warning Signal • supply-chain-risk ($0.20): Supply Chain Geopolitical Risk • regional-brief ($0.15): Regional Situational Brief

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback window in days
langNoResponse language ISO 639-1 code (en, es, fr, de, ar, zh, pt, ja, ko, ru)
yearNoElection year (e.g., 2025, 2026)
eventNoEvent to analyze (e.g., Russia-Ukraine ceasefire, Taiwan strait incident, Iran nuclear deal)
actionYesWhich endpoint to call. Options: country-risk | conflict-scan | sanctions-intel | election-watch | trade-tension | regime-brief | event-impact | instability-signal | supply-chain-risk | regional-brief
regionNoCountry or region to scan (e.g., Ukraine, Gaza, Sudan, Myanmar, Sahel)
sectorNoSector or commodity (e.g., semiconductors, rare earths, lithium, pharmaceuticals, energy, food)
targetNoCountry, entity, or individual to assess (e.g., Russia, Iran, North Korea, Huawei)
countryNoCountry name or code (e.g., Russia, China, Iran, Venezuela, Nigeria)
country_aNoFirst country (e.g., US, EU, China, India)
country_bNoSecond country (e.g., China, Russia, Taiwan, Mexico)

Schema Changelog

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

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It usefully discloses per-endpoint pricing and claims real-time global coverage, but it omits important traits such as read-only behavior, response format, rate limits, authentication needs, or data limitations. The pricing information adds some transparency beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively compact, but it includes marketing language and a truncated phrase ('for 19') that reduces clarity. The endpoint list largely duplicates the action enum, and the structure is more promotional than instructional, though it is not excessively verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, 10 endpoints, no output schema, and no annotations, the description is incomplete. It fails to explain which parameters are required or meaningful for each action, what the response looks like, or how to construct a valid request. The endpoint list alone is insufficient for an agent to reliably invoke the tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds endpoint labels and prices but does not clarify how parameters map to specific endpoints or provide additional semantic detail beyond the schema. It meets the baseline but does not compensate for ambiguity around parameter combinations.

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 identifies the tool as 'Real-time geopolitical intelligence' and enumerates 10 concrete endpoints such as country-risk, conflict-scan, and sanctions-intel, making the tool's function reasonably clear. It distinguishes itself from siblings by its geopolitical focus, though it does not explicitly contrast with other 'pulse' tools.

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?

The description provides endpoint names and prices but no guidance on when to choose this tool over sibling tools or which endpoint to use for a given scenario. It does not mention exclusions, prerequisites, or alternative tools, leaving the agent to infer usage from endpoint labels.

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

All pulsenetwork toolsInspect
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

B3.2/5.0
Disambiguation4/5

Each tool has a unique domain prefix (e.g., airdroppulse, alphapulse, arbipulse) making them mostly distinguishable at a glance. A few adjacent verticals like careerpulse vs talentpulse or marketpulse vs dealpulse have overlapping themes, but their descriptions clarify the distinct focus. The utility tools (catalog_search, discover, get_openapi_spec, x402_troubleshoot) are also clearly distinct in role. However, the sheer number of similar 'pulse' names could still cause misselection without reading descriptions.

Naming Consistency4/5

The dominant naming convention is `<domain>pulse` (e.g., climatepulse, cryptopulse, edupulse), which is highly consistent and predictable. Exceptions like catalog_search, discover, get_openapi_spec, x402_troubleshoot, and stateedge break the pattern, but these are few and serve obvious utility purposes. Overall, the convention is clear and easily learnable.

Tool Count2/5

With 80 tools, the server presents an extremely large and potentially overwhelming surface. While each tool represents a distinct intelligence vertical and navigation aids exist (catalog_search, discover, get_openapi_spec), the count far exceeds the typical 3-15 range for coherent agent use and even the 'heavy' 16-25 range. The burden of selecting the correct vertical from 80 options is significant, despite clear naming.

Completeness5/5

The server offers an exceptionally broad and deep coverage of domains, from finance and health to agriculture and gaming. Each vertical includes multiple endpoints that address core operations for its domain, such as search, analysis, comparisons, deterministic checks, and even action-oriented tools like letter generators and physical mail. The presence of free discovery and troubleshooting tools fills potential gaps, leaving no obvious dead ends in the overall tool surface.

Resources