Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

Whale stablecoin transfers: large USDC/USDT moves on Ethereum, Base, Arbitrum with entity labels and OFAC flags

stablecoin_transfers

Use when an agent tracks large stablecoin flows (whale alerts). Input: chain (ethereum, base, arbitrum), optional token (USDC, USDT), min_usd (default 100000), minutes (Ethereum ≤30, Base ≤5, Arbitrum ≤10), limit (default 25). Output: JSON transfers sorted by size with total/returned/truncated, totalUsd (returned rows) and totalUsdAll (window), from/to entity labels + OFAC flags, mint/burn, tx link. Example: ?chain=ethereum&min_usd=1000000 Price: $0.002 USDC (Base or Solana) via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stablecoin_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain (default ethereum)
limitNoMax transfers returned (default 25); total/returned/truncated report the rest
tokenNoStablecoin (default all on the chain; Base has USDC only)
min_usdNoSmallest transfer to list (default 100000)
minutesNoLook-back window (default Ethereum 10, Base 2, Arbitrum 5; max 30 / 5 / 10). Out of range → 400 before payment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Rows (default 25)"New value: +"Max transfers returned (default 25); total/returned/truncated report the rest"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the return shape (sorted by size, total/returned/truncated, totalUsd vs totalUsdAll), enrichment fields (entity labels, OFAC flags, mint/burn, tx link), per-chain window limits, the 400-before-payment error behavior, and the $0.002 USDC x402 price. It never explicitly says the tool is read-only, but the operation is inherently a query.

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?

Front-loaded with the use case, then organized as Input / Output / Example / Price, so an agent can scan it quickly. It is dense but nearly every clause carries information; the pricing sentence is the only element that feels appended rather than integrated.

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 five-parameter, no-annotation, no-output-schema tool, the description covers inputs, per-chain constraints, output fields, error behavior and payment cost. An agent can decide to call it and interpret the response without consulting anything else.

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, and the description adds real value on top: it ties limit to the total/returned/truncated accounting and restates the per-chain minutes ceilings in one place. The example (?chain=ethereum&min_usd=1000000) further anchors parameter use.

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 ('tracks large stablecoin flows (whale alerts)') and scopes it to USDC/USDT on ethereum, base, arbitrum with min_usd thresholds. That is enough to distinguish it from siblings like crypto_stablecoins, base_token_flows and stablecoin_freezes without opening a schema.

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 opening 'Use when an agent tracks large stablecoin flows' gives a clear usage context, and the example query shows a concrete invocation. It does not name an alternative tool or state when-not-to-use (e.g., small transfers or non-stablecoin flows), so it stops short of full routing guidance.

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

All 1gateway 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