Skip to main content
Glama

list_currencies

List all currencies configured for your company. Filter results using optional parameters: include, items per page, and page number.

Instructions

List company currencies. GET /currencies. Optional: include, itemPerPage, pageNo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeNoComma-separated attributes to include
itemPerPageNoItems per page
pageNoNoPage number

Implementation Reference

  • The handler function that parses arguments via the Zod schema and delegates to currencyService.listCurrencies.
    async function handler(client: Client, args: Record<string, unknown> | undefined) {
      const parsed = schema.safeParse(args);
      if (!parsed.success) {
        return errorResult(parsed.error.errors.map((e) => e.message).join("; "));
      }
      return handleToolCall(() => currencyService.listCurrencies(client, parsed.data));
    }
  • Zod schema defining input validation for the list_currencies tool (include, itemPerPage, pageNo).
    const schema = z.object({
      include: z.string().optional(),
      itemPerPage: z.number().int().min(1).optional(),
      pageNo: z.number().int().min(1).optional(),
    });
  • TypeScript interface for the parameters passed to the listCurrencies service function.
    export interface ListCurrenciesParams {
      include?: string;
      itemPerPage?: number;
      pageNo?: number;
    }
  • The Tool object that wraps the definition and handler for registration.
    export const listCurrenciesTool: Tool = {
      definition,
      handler,
    };
  • The underlying service function that makes the HTTP GET /currencies call to the API.
    export async function listCurrencies(
      client: Client,
      params?: ListCurrenciesParams
    ): Promise<unknown> {
      const search = new URLSearchParams();
      if (params?.include) search.append("include", params.include);
      if (params?.itemPerPage != null) search.append("itemPerPage", String(params.itemPerPage));
      if (params?.pageNo != null) search.append("pageNo", String(params.pageNo));
      const q = search.toString();
      return client.get<unknown>(`/currencies${q ? `?${q}` : ""}`);
    }
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It only states 'List company currencies' and the HTTP method. It does not disclose rate limits, auth requirements, sorting, default page size, or response structure.

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: one for purpose, one for parameters. No redundancy. Front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is present. The description does not mention default pagination, response format, or what the 'include' parameter controls beyond the schema. Adequate for a simple list but could clarify behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters have descriptions in the input schema (100% coverage). The description merely lists parameter names without adding further meaning. Baseline 3 is appropriate.

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 'List company currencies' and includes the HTTP method 'GET /currencies', which precisely conveys the resource and action. It distinguishes itself from sibling tools like 'get_currency' (single) and 'create_currency'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'get_currency' or filtering options. The description does not mention pagination behavior or any prerequisites.

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/rhinosaas/rebillia-mcp-server'

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