Skip to main content
Glama

EMpulse Street FX Index

by io.github.empulse-ai
OverviewDiscussionsAdmin

Unmet payment demand

get_unmet_demand

Where payment demand in emerging markets is not being served. Without a currency: the ranking of covered markets by the share of demand no rail served, with the trend. With a currency: its rank and trend (free level, one day behind); Pro keys of the Unmet Demand Map also get the unmet share, the not-connected share, the index against the 90-day norm, the reason classes and the hours of day, per direction and method class.

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the citation text (ISO 639-1 code of a site language: en, ru, es, ar, tr, uz); default English
currencyNoISO 4217 code; omit for the ranking

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose important behavior: the free level is one day behind, and Pro keys unlock additional fields. It does not mention rate limits or error behavior, but the key freshness and access-tier traits are surfaced.

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

Conciseness5/5

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

The purpose is front-loaded, then the two currency modes are presented in parallel. Despite covering freshness and plan-gated fields, every clause carries useful information and there is no filler.

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?

The description explains both modes, data freshness, and Pro-level fields, while an output schema exists to document return shape. The only gap is that the lang parameter is not discussed in the description, but the schema covers it.

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 the baseline would be 3, but the description adds meaningful semantics for the currency parameter: omitting it returns a ranking, while providing it returns rank and trend for that currency. It does not add detail for the lang parameter, but the schema already covers both.

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 states a specific domain resource — unmet payment demand in emerging markets — and precisely distinguishes the two output modes based on whether a currency is supplied. An agent can immediately tell what the tool does and how the response differs by invocation style.

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

Usage Guidelines4/5

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

It gives clear invocation context: omit currency for a ranking, provide currency for a specific market's rank and trend. It does not name alternative sibling tools or state when not to use this one, but the parameter-driven usage is explicit enough for correct selection.

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 toolsInspect
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.

Resources