Skip to main content
Glama

Stablecoin network fees

stablecoin_network_fees
Read-only

What one USDT or USDC transfer costs in network fees right now, in USD and the network's own token, on Tron, Ethereum, Solana, Base, Arbitrum, Polygon, Optimism, Avalanche and Aptos, with typical time to finality. Refreshed every 10 minutes. Network fees only, not any provider's pricing.

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_network_fees"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoOnly this token
networkNoOnly this network, e.g. tron, ethereum, solana, base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely non-obvious behavior — freshness cadence (10-minute refresh) and the fact that values cover both USD and native-token denominations plus finality time. It does not discuss caching behavior at boundaries, rate limits, or what happens for an unsupported network string, which keeps it below a 5.

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?

Two sentences, front-loaded with the core question the tool answers, then freshness and scope exclusions. Every clause carries information — chains covered, denominations, finality time, refresh interval, and the provider-pricing exclusion — with no filler.

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?

With no output schema, the description correctly carries the return burden by naming the currency denominations and the additional finality metric. It is nearly complete for a two-optional-filter read tool, but never states the unfiltered default (all tokens across all networks) explicitly, leaving the agent to infer it.

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% and both parameters are documented, so baseline is 3; the description earns above that by enumerating the full supported network set (Tron, Ethereum, Solana, Base, Arbitrum, Polygon, Optimism, Avalanche, Aptos) for a free-form string parameter that the schema only illustrates with four examples. It adds no guidance on whether the two filters can be combined or what an unmatched network returns.

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 concrete verb+resource: the current cost of one USDT/USDC transfer in network fees, denominated in USD and the native token, across nine named chains with time-to-finality. It also draws a scope boundary ('Network fees only, not any provider's pricing') that separates it from pricing/rate siblings such as stablecoin_rate and plan_offramp.

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 'right now' framing plus 'Refreshed every 10 minutes' tells the agent this is for current, near-real-time fee checks rather than historical data, and the exclusion of provider pricing clarifies the boundary. It stops short of naming an alternative tool or stating an explicit when-not condition, so it is clear context but not full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources