Skip to main content
Glama

Eagle Virtual — Stablecoin Freeze & Seize Tracker

by com.eaglevirtual

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. Each result reports which chains, coins and issuers it actually contains. This is a published sample of the record, not the full corpus, and there is no way to page beyond it. To check a specific wallet, use get_address_status instead; for totals use get_token_statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoRestrict to one kind of event.
chainNoBlockchain name or chain id, e.g. Tron or 1.
limitNoRows to return, up to 100. Defaults to 25.
sinceNoOnly events on or after this date, YYYY-MM-DD.
tokenNoCoin symbol, e.g. USDT.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses that this is a published sample rather than the full corpus, that paging is impossible, that results are newest first, and that each result reports contained chains, coins and issuers. These behavioral traits are material to calling the tool correctly and are not visible in the schema or annotations.

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 description is dense but every sentence earns its place: feed identity, row contents, coverage, ordering, filtering behavior, sample-vs-full-corpus caveat, and sibling routing. There is no repetition of schema details and no filler.

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?

For a read-only list tool with no output schema, the description covers what data is returned, the ordering, available filters, the limitation on paging, and where to go for alternative queries. An agent has enough to select and invoke it appropriately.

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 is 3. The description adds value by explaining that filters are optional, that omitting them returns everything, and that the event kinds map to filterable dimensions, which reinforces the meaning of kind, chain, token and since beyond their individual schema descriptions.

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 uses a specific verb and resource: it lists recent stablecoin blacklist, freeze, seizure, release and on-chain sanctions events from a published feed. It names the exact row fields and distinguishes itself from siblings by pointing to get_address_status and get_token_statistics as alternatives for different needs.

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?

It explicitly explains when to use this feed: for the published event list, with no paging possible, and directs to get_address_status for a specific wallet and get_token_statistics for totals. It also clarifies that omitting filters returns all events and that filters narrow by coin, blockchain, event kind or date.

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

All Eagle Virtual — Stablecoin Freeze & Seize Tracker toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a clearly distinct query type: per-address history, largest events, coverage metadata, per-coin policy, aggregate statistics, and the public event feed. Where list_freeze_events and get_address_status both return event rows, the descriptions explicitly point agents to the right tool for each use case.

Naming Consistency4/5

The naming is mostly consistent with get_* snake_case verbs, and all names are readable and predictable. Minor deviations are list_freeze_events using 'list' instead of 'get' and get_biggest being more of a query label than a resource noun.

Tool Count5/5

Six tools is well-scoped for a focused read-only tracker. Each tool earns its place and there is no redundancy or bloat.

Completeness4/5

The core domain is well covered: address lookups, token policies, aggregate statistics, coverage checks, ranked events, and a public event feed are all present. Minor gaps include no direct lookup by transaction/block/event ID and no way to page through the full historical event feed, but those limitations are clearly disclosed and do not break common workflows.

Resources