Skip to main content
Glama

geopoliticalpulse

Assess political risks, monitor conflicts, track sanctions, and analyze trade tensions with real-time geopolitical intelligence for global situational awareness.

Instructions

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)
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as rate limits, authentication requirements, error handling, or side effects. The inclusion of pricing is unusual but not about behavior.

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

Conciseness2/5

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

The description is long and reads like a product page, with unnecessary details like pricing per endpoint. It could be much shorter and more focused on the tool's function.

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?

The description explains the overall function but fails to describe return values (no output schema), constraints, or how parameters relate. For a complex tool with 11 parameters, more context is needed.

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 covers all 11 parameters with descriptions (100% coverage). The description adds a list of endpoints with pricing, which provides some extra context for the 'action' parameter, but otherwise does not add meaning beyond the schema.

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 it provides 'real-time geopolitical intelligence' and lists many endpoints, making the general purpose clear. However, it does not differentiate from siblings like policypulse or tradepulse, and the title is null.

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 geopoliticalpulse vs other pulse tools. No when-not or alternatives mentioned. The description assumes the agent infers usage from the name.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/mcp-pulsenetwork'

If you have feedback or need assistance with the MCP directory API, please join our Discord server