Skip to main content
Glama

menese_prices

Retrieve current USD prices for crypto tokens including BTC, ETH, SOL, and other major cryptocurrencies to support trading and portfolio tracking decisions.

Instructions

Get current USD prices for crypto tokens. Supports: BTC, ETH, SOL, ICP, MATIC, BNB, ADA, XRP, SUI, TON, APT, NEAR, TRX, LTC, RUNE, CLOAK, USDC, USDT, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokensYesToken symbols (e.g. ['BTC', 'ETH', 'SOL'])

Implementation Reference

  • The handler implementation for the menese_prices tool, which fetches prices from CoinGecko.
    async ({ tokens }) => {
      const ids = tokens
        .map((t) => COINGECKO_IDS[t.toLowerCase()])
        .filter(Boolean);
    
      if (ids.length === 0) {
        return {
          content: [{ type: "text" as const, text: "No recognized tokens. Try: BTC, ETH, SOL, ICP, etc." }],
          isError: true,
        };
      }
    
      const idStr = [...new Set(ids)].sort().join(",");
      const prices = await cacheFetch(
        CacheKeys.prices(idStr),
        TTL.PRICES,
        async () => {
          const url = `https://api.coingecko.com/api/v3/simple/price?ids=${idStr}&vs_currencies=usd&include_24hr_change=true`;
          const res = await fetch(url);
          if (!res.ok) throw new Error(`CoinGecko API error: ${res.status}`);
          return res.json() as Promise<Record<string, { usd: number; usd_24h_change?: number }>>;
        },
      );
    
      // Map back to user's token symbols
      const result: Record<string, { usd: number; change24h?: number }> = {};
      for (const token of tokens) {
        const id = COINGECKO_IDS[token.toLowerCase()];
        if (id && prices[id]) {
          result[token.toUpperCase()] = {
            usd: prices[id].usd,
            change24h: prices[id].usd_24h_change,
          };
        }
      }
    
      return {
        content: [{
          type: "text" as const,
          text: JSON.stringify(result, null, 2),
        }],
      };
    },
  • The input schema and tool description for menese_prices.
    {
      description:
        "Get current USD prices for crypto tokens. Supports: BTC, ETH, SOL, ICP, MATIC, BNB, " +
        "ADA, XRP, SUI, TON, APT, NEAR, TRX, LTC, RUNE, CLOAK, USDC, USDT, and more.",
      inputSchema: {
        tokens: z.array(z.string()).min(1).max(20).describe("Token symbols (e.g. ['BTC', 'ETH', 'SOL'])"),
      },
  • Registration function for the menese_prices tool.
    export function registerPricesTool(server: McpServer): void {
      server.registerTool(
        "menese_prices",
        {
          description:
            "Get current USD prices for crypto tokens. Supports: BTC, ETH, SOL, ICP, MATIC, BNB, " +
            "ADA, XRP, SUI, TON, APT, NEAR, TRX, LTC, RUNE, CLOAK, USDC, USDT, and more.",
          inputSchema: {
            tokens: z.array(z.string()).min(1).max(20).describe("Token symbols (e.g. ['BTC', 'ETH', 'SOL'])"),
          },
        },
        async ({ tokens }) => {
          const ids = tokens
            .map((t) => COINGECKO_IDS[t.toLowerCase()])
            .filter(Boolean);
    
          if (ids.length === 0) {
            return {
              content: [{ type: "text" as const, text: "No recognized tokens. Try: BTC, ETH, SOL, ICP, etc." }],
              isError: true,
            };
          }
    
          const idStr = [...new Set(ids)].sort().join(",");
          const prices = await cacheFetch(
            CacheKeys.prices(idStr),
            TTL.PRICES,
            async () => {
              const url = `https://api.coingecko.com/api/v3/simple/price?ids=${idStr}&vs_currencies=usd&include_24hr_change=true`;
              const res = await fetch(url);
              if (!res.ok) throw new Error(`CoinGecko API error: ${res.status}`);
              return res.json() as Promise<Record<string, { usd: number; usd_24h_change?: number }>>;
            },
          );
    
          // Map back to user's token symbols
          const result: Record<string, { usd: number; change24h?: number }> = {};
          for (const token of tokens) {
            const id = COINGECKO_IDS[token.toLowerCase()];
            if (id && prices[id]) {
              result[token.toUpperCase()] = {
                usd: prices[id].usd,
                change24h: prices[id].usd_24h_change,
              };
            }
          }
    
          return {
            content: [{
              type: "text" as const,
              text: JSON.stringify(result, null, 2),
            }],
          };
        },
      );
    }
Behavior3/5

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

With no annotations provided, description carries full burden. It discloses currency (USD) and freshness ('current'), but omits data source, caching behavior, rate limits, or error handling for unsupported tokens. Baseline adequacy for a read-only lookup tool.

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 with zero waste: first states purpose, second enumerates supported tokens. Information is front-loaded and appropriately sized for the tool's complexity.

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 single parameter with complete schema coverage and no output schema, description adequately covers the tool's scope. Minor gap: lacks return value description or error behavior, but this is acceptable for a simple lookup tool of this type.

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?

While schema has 100% description coverage (baseline 3), the description adds significant value by enumerating 18+ supported token symbols (BTC, ETH, etc.) that the schema lacks as enums. This helps the agent construct valid requests beyond the generic schema example.

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?

Description uses specific verb 'Get' with clear resource 'current USD prices for crypto tokens'. The token list clearly distinguishes this from trading siblings (menese_swap, menese_send) and account siblings (menese_balance, menese_portfolio).

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?

Purpose is clear enough to imply usage (use when you need price data), but lacks explicit 'when to use' guidance or comparison to siblings like menese_quote which might provide different price contexts. No alternatives or exclusions stated.

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

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/Aboodtt404/mcp-menese-sdk'

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