Skip to main content
Glama

Stablecoin networks

get_stablecoin_networks
Read-onlyIdempotent

Lists the networks that stablecoins such as USDC can be received from and sent to, with the fee and speed for each, and Poplin's home network. Use it only when someone asks about receiving or sending stablecoins.

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": "get_stablecoin_networks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing what the response contains (per-network fee and speed, plus Poplin's home network), which tells the agent this is a static reference lookup rather than a live quote.

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?

One front-loaded sentence stating what is returned, followed by one short scoping sentence. No filler, no repetition of the title, and the most decision-relevant information (the resource and its fields) comes first.

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 carries the burden of describing the return value, and it does so adequately by listing networks, fee, speed, and home network. What it leaves implicit is whether this is the exhaustive set of supported networks or whether availability varies by user/country, which matters for a tool with no parameters to narrow results.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. It correctly avoids inventing parameter talk.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Lists') and resource ('networks that stablecoins such as USDC can be received from and sent to') and even enumerates the payload fields (fee, speed, Poplin's home network). It does not, however, distinguish itself from siblings like get_stablecoin_transfer_quote or get_send_quote, which an agent could plausibly confuse with it.

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

Usage Guidelines3/5

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

It gives a scope restriction ('Use it only when someone asks about receiving or sending stablecoins'), which is genuine when-to-use guidance. But that condition overlaps heavily with the quote siblings, and no alternative is named, so an agent asking 'how do I send USDC' has no signal telling it to prefer get_send_quote or get_stablecoin_transfer_quote over this.

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.