Skip to main content
Glama

supported_currencies

Read-only

Which currencies HelloBooks bills and keeps books in. Call with no args for every supported currency grouped by code (with the countries using it and whether each is billed locally or in USD), or with a country for that country’s books currency + billing behaviour. The 8 priced regions check out in local currency; other supported countries are billed in USD while their books run in the local currency. Read-only public data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "supported_currencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code to report a single country’s currency + billing behaviour.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description reinforces this with 'Read-only public data' while adding genuinely new behavioral detail about the billing model: 8 priced regions are charged in local currency, others are billed in USD while their books stay local. That business rule is not derivable from any structured field.

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?

Three sentences, front-loaded with the resource definition, then the two call modes, then the billing rule. No filler and nothing repeated unnecessarily.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry return-value meaning, and it does: results are grouped by currency code with the countries using it and per-country billing mode. For a one-optional-param read-only lookup this leaves nothing an agent needs unstated.

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?

The single parameter has 100% schema coverage, including an enum of ISO codes and a description of its effect, so the baseline is 3. The prose restates that passing `country` yields 'that country's books currency + billing behaviour' without adding format or validation detail beyond the schema.

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?

Opens with a concrete statement of the resource ('Which currencies HelloBooks bills and keeps books in') and describes both return shapes. It is clearly distinguishable from analytics siblings, though it does not explicitly name a near-neighbor like country_support to separate the two.

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 explicitly covers both invocation modes: no args for the full grouped list, or a `country` for one country's books currency and billing behaviour. It does not name an alternative tool or state when *not* to use it, so it falls short of a 5.

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