pulsenetwork

riskpulse

RiskPulse: Global risk intelligence API. AI-synthesized travel safety alerts, country risk profiles, sanctions screening, business risk analysis, supply chain disruption intelligence, nomad visa/tax guidance, ex

Coverage: Global

Endpoints: • country ($0.10): Country risk profile • travel ($0.08): Travel safety assessment • business ($0.10): Business risk analysis • compare ($0.10): Country risk comparison • expat ($0.10): Expat living guide • alerts ($0.10): Situational security alerts • quake-check ($0.01): Earthquake activity check — deterministic USGS primitive • evac ($0.10): Evacuation plan • nomad ($0.10): Digital nomad score • sanctions ($0.15): Sanctions exposure analysis • supply ($0.15): Supply chain risk

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude of the point of interest (omit both lat and lon for the global feed)
`lon`	No	Longitude of the point of interest
`city`	No	City
`days`	No	Lookback window in days (max 365)
`from`	No	Country of origin (default: US)
`lang`	No	lang
`limit`	No	Max events returned (max 100)
`action`	Yes	Which endpoint to call. Options: country \| travel \| business \| compare \| expat \| alerts \| quake-check \| evac \| nomad \| sanctions \| supply
`entity`	No	Entity name
`country`	No	Country name (e.g. Mexico, Thailand, Nigeria)
`product`	No	Product or component
`industry`	No	industry
`location`	No	Location
`countries`	No	Comma-separated country names (e.g. Mexico,Colombia,Costa Rica)
`radius_km`	No	Search radius in km (max 5000)
`entity_type`	No	Entity type (person, company, vessel)
`nationality`	No	Traveler nationality (default: US)
`min_magnitude`	No	Minimum magnitude (default 4.0 with a point, 5.0 global)

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 21, 2026

changedInput schema / properties / days / description

Previous value: -"Lookback days (default 30, max 365)"New value: +"Lookback window in days (max 365)"

changedInput schema / properties / lat / description

Previous value: -"Latitude (omit both lat and lon for the global feed)"New value: +"Latitude of the point of interest (omit both lat and lon for the global feed)"

changedInput schema / properties / limit / description

Previous value: -"Max events (default 20, max 100)"New value: +"Max events returned (max 100)"

changedInput schema / properties / lon / description

Previous value: -"Longitude"New value: +"Longitude of the point of interest"

changedInput schema / properties / radius_km / description

Previous value: -"Search radius in km (default 500, max 5000)"New value: +"Search radius in km (max 5000)"

Changed8 schema fields changedJul 14, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: country | travel | business | compare | expat | alerts | evac | nomad | sanctions | supply"New value: +"Which endpoint to call. Options: country | travel | business | compare | expat | alerts | quake-check | evac | nomad | sanctions | supply"

changedInput schema / properties / action / enum

Previous value: -[
-  "country",
-  "travel",
-  "business",
-  "compare",
-  "expat",
-  "alerts",
-  "evac",
-  "nomad",
-  "sanctions",
-  "supply"
-]New value: +[
+  "country",
+  "travel",
+  "business",
+  "compare",
+  "expat",
+  "alerts",
+  "quake-check",
+  "evac",
+  "nomad",
+  "sanctions",
+  "supply"
+]

addedInput schema / properties / days

Added value: +{
+  "description": "Lookback days (default 30, max 365)",
+  "type": "string"
+}

addedInput schema / properties / lat

Added value: +{
+  "description": "Latitude (omit both lat and lon for the global feed)",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Max events (default 20, max 100)",
+  "type": "string"
+}

addedInput schema / properties / lon

Added value: +{
+  "description": "Longitude",
+  "type": "string"
+}

addedInput schema / properties / min_magnitude

Added value: +{
+  "description": "Minimum magnitude (default 4.0 with a point, 5.0 global)",
+  "type": "string"
+}

addedInput schema / properties / radius_km

Added value: +{
+  "description": "Search radius in km (default 500, max 5000)",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It adds useful context: 'AI-synthesized' alerts, 'deterministic USGS primitive' for quake-check, and per-endpoint pricing. However, it omits response formats, auth requirements, and error behaviors, so transparency is partial.

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-structured with a front-loaded summary and a bulleted endpoint list. Each line adds value (capability and price), and the length is appropriate for an 11-endpoint tool. Slight verbosity from pricing is acceptable.

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?

This is a complex multi-action tool with 18 parameters and no output schema. The description fails to explain which parameters are relevant for each action (e.g., 'countries' for compare, 'entity' for sanctions). Without this mapping, an agent may struggle to invoke the correct endpoint with the right parameters.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by associating each action enum value with a one-line semantic and price, improving the agent's understanding of what each endpoint does. It does not map specific parameters to actions, but the parameter names are self-descriptive.

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 is a 'Global risk intelligence API' and enumerates specific capabilities (travel safety alerts, country risk profiles, sanctions screening, etc.), making it distinct from sibling tools with different domains. The verb is implicit but the resource and scope are explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists endpoints and their purposes, implying when to use the tool (e.g., for country risk, travel safety). However, it provides no explicit when-not-to-use guidance or mentions alternative sibling tools, so the agent must infer selection based on the endpoint list alone.

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

All pulsenetwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

riskpulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources