Skip to main content
Glama

get_currencies

Retrieve currency codes, symbols, and units to ensure accurate salary updates in job applications and compensation tracking.

Instructions

Get the list of supported currencies with their codes, symbols, and units. Use this to look up the correct currency code before updating salary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the get_currencies tool.
    server.tool(
      'get_currencies',
      'Get the list of supported currencies with their codes, symbols, and units. Use this to look up the correct currency code before updating salary.',
      {},
      async () => {
        const currencies = await client.getCurrencies();
        return { content: [{ type: 'text' as const, text: JSON.stringify(currencies, null, 2) }] };
      }
    );
  • The underlying implementation that fetches currency data from the API.
    async getCurrencies(): Promise<Currency[]> {
      return this.get<Currency[]>('/currencies');
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies this is a read-only operation ('Get the list'), but doesn't explicitly state whether it requires authentication, has rate limits, or describes the return format. The description adds some context about the tool's purpose but lacks comprehensive behavioral details.

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 perfectly concise with two sentences that each serve distinct purposes: the first defines what the tool does, the second provides usage guidance. There's zero wasted language, and the most important information (the tool's purpose) comes first.

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?

For a simple read operation with no parameters and no output schema, the description provides adequate context about what data is returned (codes, symbols, units) and when to use it. However, without annotations or output schema, it could benefit from more detail about the return format or any limitations.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and usage. This meets the baseline expectation for parameterless tools.

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 verb 'Get' and the resource 'list of supported currencies', specifying what information is included (codes, symbols, and units). It distinguishes this tool from siblings like get_salary or get_profile by focusing specifically on currency data.

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?

The description provides explicit guidance on when to use this tool ('to look up the correct currency code before updating salary'), which connects it to the update_salary sibling. However, it doesn't explicitly state when NOT to use it or mention alternatives for currency-related operations.

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/6figr-com/job-gpt-mcp-server'

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