Skip to main content
Glama

create_currency

Creates a new company currency by specifying a global currency ID, conversion rate, and whether the rate is fixed.

Instructions

Create a company currency. POST /currencies. Required: currencyId (global currency ID), conversionRate (number), fixedRate (boolean).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyIdYesGlobal currency ID (required)
conversionRateYesConversion rate (required)
fixedRateYesFixed rate flag (required)

Implementation Reference

  • Handler function for the create_currency tool. Validates input via Zod schema, then calls currencyService.createCurrency to POST /currencies.
    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.createCurrency(client, parsed.data));
    }
  • Zod input validation schema for create_currency: currencyId (positive int), conversionRate (finite number), fixedRate (boolean).
    const schema = z.object({
      currencyId: z.number().int().positive("currencyId is required (global currency ID)"),
      conversionRate: z.number().finite("conversionRate is required"),
      fixedRate: z.boolean({ required_error: "fixedRate is required (boolean)" }),
    });
  • Tool definition/inputSchema for MCP registration: name 'create_currency', description, and JSON Schema properties.
    const definition = {
      name: "create_currency",
      description:
        "Create a company currency. POST /currencies. Required: currencyId (global currency ID), conversionRate (number), fixedRate (boolean).",
      inputSchema: {
        type: "object" as const,
        properties: {
          currencyId: { type: "number", description: "Global currency ID (required)" },
          conversionRate: { type: "number", description: "Conversion rate (required)" },
          fixedRate: { type: "boolean", description: "Fixed rate flag (required)" },
        },
        required: ["currencyId", "conversionRate", "fixedRate"],
      },
    };
  • Registration of createCurrencyTool in the registerCurrencyTools() array alongside all other currency tools.
    export function registerCurrencyTools(): Tool[] {
      return [
        listCurrenciesTool,
        getCurrencyTool,
        createCurrencyTool,
        updateCurrencyTool,
        deleteCurrencyTool,
        getDefaultCurrencyTool,
        setDefaultCurrencyTool,
      ];
    }
  • Service-layer helper that performs the actual POST /currencies API call via the client.
    /** POST /currencies */
    export async function createCurrency(
      client: Client,
      body: CreateCurrencyBody
    ): Promise<unknown> {
      return client.post<unknown>("/currencies", body);
    }
Behavior3/5

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

No annotations provided. The description states 'POST /currencies' implying creation, and lists required fields. However, it lacks disclosure of return values, side effects, or other behaviors.

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 only, front-loaded with purpose. No redundant information, every sentence earns its place.

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?

Covers purpose and parameters but lacks return value, potential errors, or usage scenario. Adequate for a simple 3-param tool with no output schema, but not fully complete.

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 description coverage is 100% (all params described). The description repeats parameter names and types, adding minimal extra meaning beyond the schema, so baseline 3.

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 starts with 'Create a company currency,' clearly stating the action and resource. It also mentions the HTTP method and endpoint, distinguishing it from siblings like 'delete_currency' and 'update_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 vs alternatives. No prerequisites or context provided, despite siblings like 'update_currency' and 'delete_currency' existing.

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