Skip to main content
Glama

Eagle Virtual — Stablecoin Freeze & Seize Tracker

by com.eaglevirtual

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

TableJSON Schema
NameRequiredDescriptionDefault
chainNoOptional blockchain name or chain id, e.g. Ethereum or 1.
tokenNoOptional coin symbol, e.g. USDT. Omit for every coin.
group_byNoWhich breakdown to return. Defaults to token.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations by stating that only counts and dates are returned and that wallet addresses are intentionally omitted.

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?

Three focused sentences, front-loaded with the core purpose, followed by concrete examples and a clarifying limitation. Every sentence earns its place.

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 simple, fully optional-parameter read-only tool, the description is complete: it covers purpose, supported grouping, example queries, and return scope. The absent output schema is mitigated by the explicit 'counts and dates only' statement.

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 chain, token, and group_by. The description's grouping examples reinforce the group_by enum values but do not add meaningful new parameter semantics beyond what the schema provides.

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 and resource: 'Counts of recorded stablecoin blacklistings, freezes and seizures'. The examples and explicit 'no wallet addresses' note clearly distinguish it from sibling tools like list_freeze_events and get_address_status.

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 description gives concrete example questions and grouping dimensions, making it clear this tool is for aggregate statistics rather than individual records. It does not explicitly name alternatives or exclusion conditions, so it falls short of a 5.

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