Skip to main content
Glama

Eagle Virtual USDT & USDC Blacklist Tracker

by com.eaglevirtual
OverviewDiscussionsAdmin

Recent stablecoin blacklistings and freezes

list_freeze_events
Read-onlyIdempotent

The published feed of recent stablecoin blacklist, freeze, seizure, release and on-chain sanctions events, the same rows eaglevirtual.com shows publicly, with the wallet, coin, blockchain, date, block and transaction for each. Covers every coin on every chain: omit the filters and it returns all of them, newest first. Filter by coin, blockchain, event kind or date to narrow it. This is a published sample of the record, not the full corpus, and there is no way to page beyond it. Add month (YYYY-MM) for one whole recorded month: every caller gets the month’s totals, and the events behind them need a paid account. To check a specific wallet, use get_address_status; for totals use get_token_statistics.

Input Schema

NameRequiredDescriptionDefault
kindNoRestrict to one kind of event. "blacklist" is a deny-list entry in the token contract; "freeze" locks an account; "seizure" took the balance; "release" lifted a restriction; "sanctions" is an on-chain sanctions listing; "delisting" removed one. Omit for all.
chainNoBlockchain name or chain id, e.g. Tron or 1.
limitNoRows to return, up to 100. Defaults to 25.
monthNoOne whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them need a paid account.
sinceNoOnly events on or after this date, YYYY-MM-DD.
tokenNoCoin symbol, e.g. USDT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / month / description
      Previous value: -"One whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them come with the Business plan."New value: +"One whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them need a paid account."
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"Restrict to one kind of event."New value: +"Restrict to one kind of event. \"blacklist\" is a deny-list entry in the token contract; \"freeze\" locks an account; \"seizure\" took the balance; \"release\" lifted a restriction; \"sanctions\" is an on-chain sanctions listing; \"delisting\" removed one. Omit for all."
  3. Changed1 schema field changed
    • changedInput schema / properties / month / description
      Previous value: -"One whole recorded month, YYYY-MM, instead of the recent feed. Without an account the last 6 months can be listed, with a free account the last 12 months, and every month on the Business plan."New value: +"One whole recorded month, YYYY-MM, instead of the recent feed. Every caller gets the month’s totals; the events behind them come with the Business plan."
  4. Changed1 schema field changed
    • addedInput schema / properties / month
      Added value: +{
+  "description": "One whole recorded month, YYYY-MM, instead of the recent feed. Without an account the last 6 months can be listed, with a free account the last 12 months, and every month on the Business plan.",
+  "maxLength": 7,
+  "minLength": 7,
+  "pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
+  "type": "string"
+}
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only cover read-only/idempotent/openWorld=false), it discloses that this is a published sample rather than the full corpus, that there is no pagination past it, and that month totals are public while the underlying events require a paid account — critical expectations an agent would otherwise get wrong.

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?

Dense and front-loaded with scope and returned fields before the filtering guidance and alternatives. Slightly long, but nearly every clause carries distinct information; no filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by naming the returned fields (wallet, coin, blockchain, date, block, transaction) and by disclosing the sample/pagination and paid-tier limitations. Nothing an agent needs to call this correctly is missing.

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 each parameter is already documented, but the description adds real semantics: filter combinations, the newest-first ordering, and the non-obvious behavior of month (returns totals only, events gated behind paid access). It does not repeat syntax already in the schema.

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?

States a specific verb+resource (published feed of stablecoin blacklist/freeze/seizure/release/sanctions events) and immediately distinguishes itself from siblings by naming get_address_status and get_token_statistics with their respective roles.

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

Usage Guidelines5/5

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

Explicitly covers the default behavior (omit filters returns everything, newest first), the narrowing options, and two alternative tools with the conditions that select them. An agent can route correctly without opening another schema.

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