Skip to main content
Glama

Eagle Virtual USDT & USDC Blacklist Tracker

by com.eaglevirtual
OverviewDiscussionsAdmin

Stablecoin blacklist and freeze statistics

get_token_statistics
Read-onlyIdempotent

Counts of recorded stablecoin blacklistings, freezes and seizures — by coin, by blockchain, by month, or by year. Answers questions like "how many wallets has Tether blacklisted", "which coin is frozen most often", and "how many seizures happened in 2025". Returns counts and dates only; no wallet addresses are returned by this tool.

Input Schema

NameRequiredDescriptionDefault
chainNoOptional blockchain name or chain id, e.g. Ethereum or 1.
limitNoHow many coins the by-coin breakdown returns, the coins with the most recorded events first. Defaults to 20, up to 200. The totals count every coin whatever the limit. The other breakdowns are short and are returned whole.
tokenNoOptional coin ticker, e.g. USDT. A ticker two issuers use returns both coins, each with its issuer. Omit for every coin.
group_byNoWhich breakdown to return. Defaults to token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many coins the by-coin breakdown returns, the coins with the most recorded events first. Defaults to 20, up to 200. The totals count every coin whatever the limit. The other breakdowns are short and are returned whole.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / token / description
      Previous value: -"Optional coin ticker, e.g. USDT. A ticker two companies use returns both coins, each with its company. Omit for every coin."New value: +"Optional coin ticker, e.g. USDT. A ticker two issuers use returns both coins, each with its issuer. Omit for every coin."
  3. Changed1 schema field changed
    • changedInput schema / properties / token / description
      Previous value: -"Optional coin symbol, e.g. USDT. Omit for every coin."New value: +"Optional coin ticker, e.g. USDT. A ticker two companies use returns both coins, each with its company. Omit for every coin."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already grant readOnly/idempotent/non-destructive, so the bar is lower. The description adds the crucial disclosure that output is aggregate counts and dates with no wallet addresses — a real expectation-setter beyond what the annotations say. It does not describe pagination or response shape, but for an aggregate tool that is minor.

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?

Two sentences, front-loaded with the core purpose followed by concrete examples. Slightly long in the example list but every clause earns its place and nothing is redundant.

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?

Complete enough for a 4-parameter, no-required-argument read tool: the description conveys scope, breakdown options, and output character. Without an output schema, a sentence on response shape (counts + dates) is present, though not a full return-value description.

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 already documents all four parameters, including the limit semantics and enum values. The description adds no syntax or format detail beyond the schema; baseline 3 is correct.

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?

Starts with a specific verb+resource ('Counts of recorded stablecoin blacklistings, freezes and seizures') and names all four breakdown axes. The example questions concretize the scope and distinguish it from the sibling list_freeze_events, which returns event rows rather than aggregates.

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?

The three example questions make the usage context explicit, and 'Returns counts and dates only; no wallet addresses are returned' tells the agent when this tool is NOT the right choice versus an event-listing tool. It never names list_freeze_events directly, so routing is inferred rather than stated.

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

All Eagle Virtual USDT & USDC Blacklist Tracker 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