Skip to main content
Glama

EMpulse Street FX Index

by io.github.empulse-ai
OverviewDiscussionsAdmin

USDT liquidity of a currency

get_usdt_liquidity

Where and when the dollar actually moves through USDT: the liquidity index of a currency (0–100, 50 = the market's own 90-day norm) with a ready citation. Free level: yesterday, the free currencies. Pro keys of USDT Liquidity & Premium: today, every currency, the pay-in / payout balance, the spread, the active hours of day, the premium over the official rate and the supply 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
currencyYesISO 4217 code, for example EGP, NGN, ARS

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

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 full burden. It discloses access tiers (free vs Pro), data freshness (yesterday vs today), and that a citation is included. It does not mention error behavior or explicitly state that the operation is read-only, but the access-level details add meaningful context beyond the schema.

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 a single paragraph that front-loads the core purpose, though the opening phrase 'Where and when the dollar actually moves through USDT' is slightly verbose. Both sentences earn their place by covering the core output and access tiers, with no redundant information.

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?

Given the tool's simplicity (2 parameters, output schema present), the description is largely complete: it explains the main output, the scale, and what Pro adds. It could be improved by explicitly noting that the operation is read-only or by giving a hint about the response structure, but for a simple read tool it is sufficient.

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%, so the schema fully documents both parameters. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states the resource: the liquidity index of a currency, including its scale (0–100, 50 = 90-day norm) and the inclusion of a citation. It distinguishes itself from siblings by focusing on USDT liquidity, though it does not explicitly contrast with any sibling tool.

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?

It describes what data is available at the free level versus Pro keys, which implicitly suggests when to use the tool based on access. However, it does not explicitly state when to choose this tool over alternatives like get_street_rate or get_official_vs_street, nor does it mention any prerequisites beyond key level.

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