Skip to main content
Glama

get_currency

Retrieve a company's currency details using its unique currency ID.

Instructions

Get a company currency by ID. GET /currencies/{currencyId}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyIdYesCompany currency ID (required)

Implementation Reference

  • Handler function that validates args with Zod schema, then calls currencyService.getCurrency to fetch a company currency by ID.
    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.getCurrency(client, parsed.data.currencyId)
      );
    }
  • Zod validation schema for get_currency tool: requires a non-empty currencyId string.
    const schema = z.object({
      currencyId: z.string().min(1, "currencyId is required (company currency ID)"),
    });
  • Export of the Tool object combining definition and handler for get_currency.
    export const getCurrencyTool: Tool = {
      definition,
      handler,
    };
  • Service helper: makes a GET /currencies/{currencyId} API call to fetch a company currency by ID.
    export async function getCurrency(
      client: Client,
      currencyId: string
    ): Promise<unknown> {
      return client.get<unknown>(`/currencies/${currencyId}`);
    }
Behavior2/5

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

Beyond stating it is a 'get' (read) operation, the description discloses no behavioral traits such as error conditions, idempotency, response format, or authentication needs. With no annotations, the full burden falls on the description, which is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single sentence plus the HTTP endpoint. It is efficient but could improve by adding a brief note on expected output or usage context without sacrificing brevity.

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?

Given the tool's simplicity (one required parameter, no output schema), the description provides the essential information to perform the retrieval. However, it lacks any mention of return value structure or potential limitations, making it minimally viable.

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?

Schema coverage is 100% and the parameter 'currencyId' is already well-documented in the schema as 'Company currency ID (required)'. The description adds no additional meaning, so a baseline of 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 the action ('Get a company currency by ID') and the resource, distinguishing it from sibling tools like list_currencies or create_currency. The inclusion of the HTTP endpoint reinforces the specific retrieval operation.

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 is provided on when to use this tool versus alternatives such as list_currencies or get_default_currency. The description does not mention exclusions or prerequisites, leaving the agent without context for selection.

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