Skip to main content
Glama

get_default_currency

Retrieve the default currency for your company to ensure accurate billing and financial reporting.

Instructions

Get the company default currency. GET /currencies/default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the get_default_currency tool logic. It delegates to currencyService.getDefaultCurrency(client).
    async function handler(client: Client, _args: Record<string, unknown> | undefined) {
      return handleToolCall(() => currencyService.getDefaultCurrency(client));
    }
  • Input schema definition for the tool. No input parameters required (empty object).
    const definition = {
      name: "get_default_currency",
      description: "Get the company default currency. GET /currencies/default.",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    };
  • The tool is registered via registerCurrencyTools() which returns an array including getDefaultCurrencyTool.
    export function registerCurrencyTools(): Tool[] {
      return [
        listCurrenciesTool,
        getCurrencyTool,
        createCurrencyTool,
        updateCurrencyTool,
        deleteCurrencyTool,
        getDefaultCurrencyTool,
        setDefaultCurrencyTool,
      ];
    }
  • Import statement registering getDefaultCurrencyTool from its module.
    import { getDefaultCurrencyTool } from "./getDefaultCurrency.js";
  • The service helper that makes the actual HTTP GET request to /currencies/default endpoint.
    export async function getDefaultCurrency(client: Client): Promise<unknown> {
      return client.get<unknown>("/currencies/default");
    }
Behavior3/5

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

No annotations exist. The description includes the HTTP method and endpoint, adding some transparency, but does not disclose error handling, authentication, or side effects. Minimal behavioral context.

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 concise sentences, immediately clear. No fluff, well front-loaded.

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?

No output schema exists, but for a trivial get operation with no parameters, the description is mostly complete. Could mention return format, but not essential.

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?

Input schema has no parameters and 100% coverage. Baseline 3 applies; the description does not add extra semantics beyond what the schema provides.

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 it retrieves the company default currency, using specific verb and resource. It distinguishes itself from siblings like 'get_currency' (likely for specific currency) and 'list_currencies'.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, the context implies it's for the default currency, not for specific ones. Could be improved with alternatives mention.

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