Skip to main content
Glama
kukapay

crypto-pegmon-mcp

get_supported_stablecoins

Retrieve a Markdown-formatted table of USD-pegged stablecoins, including their symbols and descriptions, to simplify tracking and analysis.

Instructions

Fetch the list of supported USD-pegged stablecoins with their symbols and descriptions.

Returns:
    str: A Markdown-formatted table listing stablecoin symbols and their descriptions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:87-103 (handler)
    The handler function decorated with @mcp.tool(), implementing the logic to return a Markdown table of supported USD-pegged stablecoins using pandas and the STABLECOINS dictionary.
    @mcp.tool()
    def get_supported_stablecoins() -> str:
        """
        Fetch the list of supported USD-pegged stablecoins with their symbols and descriptions.
    
        Returns:
            str: A Markdown-formatted table listing stablecoin symbols and their descriptions.
        """
        # Create DataFrame for stablecoins and descriptions
        df = pd.DataFrame([
            {"Symbol": coin.upper(), "Description": STABLECOINS[coin]["description"]}
            for coin in STABLECOINS.keys()
        ])
        
        # Convert to Markdown table
        markdown_table = df.to_markdown(index=False)
        return f"**Supported USD-Pegged Stablecoins**:\n\n{markdown_table}"
  • main.py:15-84 (helper)
    Global dictionary defining all supported stablecoins with CoinGecko IDs and descriptions, directly used by the get_supported_stablecoins handler.
    STABLECOINS = {
        "usdt": {
            "id": "tether",
            "description": "Tether's USD-pegged stablecoin, centrally issued."
        },
        "usdc": {
            "id": "usd-coin",
            "description": "Circle's USD-backed stablecoin, widely used in DeFi."
        },
        "dai": {
            "id": "dai",
            "description": "Decentralized stablecoin by MakerDAO, collateralized by crypto."
        },
        "busd": {
            "id": "binance-usd",
            "description": "Binance's USD-pegged stablecoin, centrally managed."
        },
        "tusd": {
            "id": "true-usd",
            "description": "TrueUSD, a USD-backed stablecoin by TrustToken."
        },
        "frax": {
            "id": "frax",
            "description": "Fractional-algorithmic USD stablecoin by Frax Finance."
        },
        "usdd": {
            "id": "usdd",
            "description": "TRON's USD-pegged stablecoin, centrally issued."
        },
        "usds": {
            "id": "usds",
            "description": "USD-pegged stablecoin, focused on stability."
        },
        "susds": {
            "id": "susds",
            "description": "Staked USDS, yield-bearing stablecoin."
        },
        "eusde": {
            "id": "ethena-staked-usde",
            "description": "Ethena's staked USD stablecoin, yield-bearing."
        },
        "usdy": {
            "id": "ondo-us-dollar-yield",
            "description": "Ondo's USD yield stablecoin, designed for returns."
        },
        "pyusd": {
            "id": "paypal-usd",
            "description": "PayPal's USD-pegged stablecoin for payments."
        },
        "gusd": {
            "id": "gemini-dollar",
            "description": "Gemini Dollar, USD-backed by Gemini Trust."
        },
        "usdp": {
            "id": "paxos-standard",
            "description": "Paxos Standard, a regulated USD stablecoin."
        },
        "aave-usdc": {
            "id": "aave-usdc",
            "description": "Aave's USD-pegged stablecoin for lending."
        },
        "curve-usd": {
            "id": "curve-usd",
            "description": "Curve Finance's USD stablecoin for DeFi pools."
        },
        "mim": {
            "id": "magic-internet-money",
            "description": "Magic Internet Money, a decentralized USD stablecoin."
        }
    }
  • main.py:87-87 (registration)
    The @mcp.tool() decorator registers the get_supported_stablecoins function as an MCP tool.
    @mcp.tool()
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format ('Markdown-formatted table') and content ('symbols and descriptions'), which is useful behavioral context. However, it does not mention other traits like rate limits, authentication needs, or error handling, leaving gaps for a tool with no 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 front-loaded with the core purpose in the first sentence, followed by a concise return specification. Both sentences earn their place by providing essential information without redundancy, making it highly efficient and well-structured.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is mostly complete: it states the purpose, return format, and content. However, without annotations, it could benefit from mentioning behavioral aspects like safety or performance, but for a read-only list tool, this is a minor gap.

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 has 0 parameters, and schema description coverage is 100% (as there are no parameters to describe). The description does not need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as per the rules.

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 clearly states the verb ('Fetch') and resource ('list of supported USD-pegged stablecoins'), specifying both the scope ('USD-pegged') and the content ('symbols and descriptions'). It distinguishes from siblings like 'analyze_peg_stability' (which analyzes rather than lists) and 'get_current_price' (which fetches prices rather than metadata).

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?

The description implies usage by stating what the tool returns (a Markdown table of stablecoin data), but it does not explicitly guide when to use this tool versus alternatives like 'get_current_price' for price data or 'analyze_peg_stability' for stability analysis. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/crypto-pegmon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server