Skip to main content
Glama

YESbusiness

Available currencies

list_available_currencies
Read-onlyIdempotent

The catalog of currencies the company could activate (id, symbol, localized name). Use it to check whether a currency the user names exists and to get its exact symbol.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "list_available_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_idYesThe company to work on — one of list_my_companies' company_id values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered. The description adds the behavioral nuance that this is a candidate/activatable catalog rather than the company's active settings, and that results carry localized names. It says nothing about how many currencies come back or whether inactive ones are filtered.

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 short sentences: the first defines the resource and its fields, the second states the use case. Nothing is repeated and the most decision-relevant fact (this is a catalog of activatable currencies) is 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?

There is no output schema, but the description enumerates the returned fields (id, symbol, localized name), which covers the return value. For a one-parameter read-only lookup with full annotations, the only material gap is the missing contrast with get_currency_settings.

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 single company_id parameter is already documented, including where its value comes from (list_my_companies). The description adds no meaning to the parameter beyond the schema, so the high-coverage baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and its scope: the catalog of currencies the company *could activate*, with the returned fields (id, symbol, localized name). This implicitly separates it from get_currency_settings, which the sibling list suggests handles the currently configured state, but that distinction is never stated outright.

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?

It gives two concrete use cases: validating that a user-named currency exists and retrieving its exact symbol. It does not, however, state when to prefer get_currency_settings over this tool, leaving the most plausible sibling choice to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources