EMpulse Street FX Index

Payment rails of a country today

get_rail_health

Which payment methods work in a country today and how reliably: for every method class (cards, bank transfers, instant transfers, e-wallets, mobile money, cash, crypto, direct local rails) and direction (pay-ins, payouts) a status — healthy / degraded / outage / no_data — with the time it began and a ready citation. Free level: the free currencies, one day behind. Pro keys of the Rail Health Index: today, every currency, the health index (100 = the rail's own norm), availability, supply.

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English
`currency`	Yes	ISO 4217 code, for example EGP, NGN, ARS

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / lang

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Language of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English",
+  "title": "Lang"
+}

First observedOct 26, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the four possible statuses, what each entry contains (time began, ready citation), and a real access constraint (free level is one day behind and limited currencies; Pro keys unlock today/every currency/index/availability/supply). It stops short of explicit auth mechanism or rate-limit detail.

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?

Front-loads the purpose in the first clause, then the status/coverage framing, then the tier distinction. The long enumerations (method classes, statuses) are dense but each clause carries information; no filler sentences.

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?

An output schema exists, so return values need not be spelled out, yet the description usefully previews the shape and the free/Pro data boundary. Combined with full schema coverage, an agent has enough to invoke it correctly; only sibling routing is missing.

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%, and both currency (ISO 4217) and lang (ISO 639-1) are fully documented in the schema. The description adds no parameter-level meaning beyond establishing that a single country/currency is the subject.

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?

States a specific verb+resource: which payment methods work in a country today, broken down by method class and direction, with statuses. An agent can tell it apart from incident/stress siblings conceptually, but no sibling is named for explicit contrast.

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?

Usage context is implied through the free-vs-Pro tier framing (free = free currencies one day behind; Pro keys = today, every currency), but there is no explicit 'use this when X, use get_rail_incidents when Y' routing against the numerous siblings.

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

All EMpulse Street FX Index 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.