Skip to main content
Glama

econsignalpulse

Analyze economic divergence and risks in 190+ countries using satellite nightlights, AIS shipping signals, and official data from World Bank and IMF.

Instructions

EconSignalPulse: Alternative economic intelligence API covering 190+ countries. Combines World Bank Open Data, IMF Datamapper forecasts, satellite nighttime lights research, and AIS shipping signals to produce institu

Coverage: Global

Endpoints: • nightlights ($0.15): Satellite nighttime lights vs official GDP • gdp-tracker ($0.10): GDP tracker — history + IMF forecasts • inflation-signals ($0.08): Multi-source inflation signals • country-brief ($0.25): Full sovereign intelligence brief • divergence ($0.20): Official stats vs alternative data divergence • recession-signals ($0.15): Recession probability signals • frontier-intel ($0.15): Frontier and emerging market intelligence • trade-flows ($0.15): Global trade flow analysis • credit-stress ($0.15): Sovereign credit and banking stress • sanctions-impact ($0.20): Sanctions impact measurement

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iso2NoISO2 country code for World Bank data — e.g. IN | BR | DE | NG
iso3NoISO3 country code for IMF data — e.g. IND | BRA | DEU | NGA
langNoResponse language
lensNoIntelligence lens
focusNoAnalysis focus area
actionYesWhich endpoint to call. Options: nightlights | gdp-tracker | inflation-signals | country-brief | divergence | recession-signals | frontier-intel | trade-flows | credit-stress | sanctions-impact
periodNoAnalysis period
regimeNoSanctions regime to analyze
countryNoCountry name — e.g. 'India' | 'Brazil' | 'Germany' | 'Nigeria'
partnerNoOptional trade partner country for bilateral analysis — e.g. 'United States' | 'China' | 'Germany'
Behavior3/5

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

The description includes per-endpoint pricing, which is a behavioral disclosure, but lacks information on rate limits, authentication, or side effects; no annotations are provided to supplement.

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 well-organized with a clear endpoint list, but the truncated first sentence and repeated pricing information detract slightly from conciseness.

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?

For a tool with 10 parameters and no output schema, the description fails to explain parameter dependencies, output format, or usage patterns, making it incomplete.

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?

The input schema has 100% description coverage, so the description adds little beyond what the schema already provides for parameters.

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 clearly identifies the tool as an alternative economic intelligence API with global coverage and specific data sources, but the introductory sentence is truncated, slightly reducing completeness.

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 lists endpoints and pricing but provides no guidance on when to use this tool versus sibling pulse tools, nor any conditions for selecting specific endpoints.

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