Skip to main content
Glama
UniRate-API

UniRate MCP

Official
by UniRate-API

List supported currencies

list_currencies
Read-only

Get a complete list of supported currency codes, including over 170 fiat currencies and major cryptocurrencies, from the UniRate API.

Instructions

Return the list of currency codes supported by the UniRate API (170+ fiat plus major crypto).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that executes the 'list_currencies' tool logic. It calls client.getSupportedCurrencies() and returns a formatted string with the count and list of currency codes.
      async () => {
        try {
          const currencies = await client.getSupportedCurrencies();
          return ok(
            `${currencies.length} currencies supported: ${currencies.join(", ")}`,
            { count: currencies.length, currencies },
          );
        } catch (err) {
          return fail(err);
        }
      },
    );
  • The input schema for 'list_currencies'. No input parameters are required (empty inputSchema object). Includes title, description, and annotations.
    {
      title: "List supported currencies",
      description:
        "Return the list of currency codes supported by the UniRate API (170+ fiat plus major crypto).",
      inputSchema: {},
      annotations: { readOnlyHint: true, openWorldHint: true },
  • src/index.ts:159-179 (registration)
    The tool registration via server.registerTool('list_currencies', ...) which registers the tool name, schema, and handler on the MCP server.
    server.registerTool(
      "list_currencies",
      {
        title: "List supported currencies",
        description:
          "Return the list of currency codes supported by the UniRate API (170+ fiat plus major crypto).",
        inputSchema: {},
        annotations: { readOnlyHint: true, openWorldHint: true },
      },
      async () => {
        try {
          const currencies = await client.getSupportedCurrencies();
          return ok(
            `${currencies.length} currencies supported: ${currencies.join(", ")}`,
            { count: currencies.length, currencies },
          );
        } catch (err) {
          return fail(err);
        }
      },
    );
  • The client method getSupportedCurrencies() that performs the actual API call to /api/currencies to retrieve the list of supported currency codes.
    async getSupportedCurrencies(): Promise<string[]> {
      const data = await this.request<{ currencies: string[] }>("/api/currencies", {});
      return data.currencies;
    }
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint; the description adds the count and types of currencies, providing useful context beyond the 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 a single sentence that is direct and front-loaded, with no unnecessary words.

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?

Given no parameters and no output schema, the description fully informs the agent about the tool's purpose and output.

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?

No parameters exist, so the schema covers 100%; baseline for zero parameters is 4, and the description omits irrelevant parameter details.

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 'Return the list of currency codes' and specifies the scope '170+ fiat plus major crypto', distinguishing it from sibling tools for conversion and rates.

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?

While no explicit when-to-use guidance is given, the simple nature and clear context make it obvious this tool is for obtaining supported currencies before using other tools.

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/UniRate-API/unirate-mcp'

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