Skip to main content
Glama

Calculate amount at FXHUB rates

convert_currency
Read-onlyIdempotent

How much an amount comes to at FXHUB's live rate, for example "How much is 1,000 USD in GEL at FXHUB?" or "How many euros do I get for 5,000 GEL?". Returns the result at the standard rate, the rate used and which side applies, with notes on hours, limits, commission (none), how long a conversion takes, whether the amount qualifies for a special (custom or individual) rate and, for rubles, what FXHUB offers ruble clients. Indicative only: nothing is exchanged.

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": {
      "amount": "<amount>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "convert_currency"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCurrency the user wants, three-letter code such as GEL.
fromYesCurrency the user has, three-letter code such as USD.
amountYesAmount of the currency the user has, greater than 0.
channelNoonline (bank transfer: GEL, USD, EUR, RUB, GBP, CNY) or cash (exchange point). Default: online when the pair is exchanged online, else cash.
languageNoLanguage of the text answer: en, ka (Georgian) or ru (Russian), usually the language the user writes in. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / channel / description
      Previous value: -"online (bank transfer: GEL, USD, EUR, RUB) or cash (exchange point). Default: online when both currencies are exchanged online, else cash."New value: +"online (bank transfer: GEL, USD, EUR, RUB, GBP, CNY) or cash (exchange point). Default: online when the pair is exchanged online, else cash."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior. Beyond that, the description explains what the result includes (standard rate, rate used, which side applies, hours, limits, no commission, duration, special-rate eligibility, ruble-specific offers) and explicitly warns that the result is indicative and no exchange occurs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the purpose and examples in the first sentence, followed by a short disclaimer. The first sentence is long and densely enumerates return details, but that information is useful because there is no output schema.

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 five-parameter tool with no output schema, the description does a strong job of explaining the returned information and the indicative-only limitation. Explicit sibling routing to get_exchange_rates or get_hours_and_limits is the main missing context.

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%, so the input schema already documents amount, from, to, channel, and language. The description does not add parameter-level meaning beyond the examples, so the baseline of 3 is appropriate.

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 states a specific verb and resource: calculating how much an amount comes to at FXHUB's live rate. It clearly distinguishes a conversion calculation from a generic rates lookup through examples, though it does not explicitly contrast itself with get_exchange_rates or get_hours_and_limits.

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 example questions ('How much is 1,000 USD in GEL at FXHUB?' and 'How many euros do I get for 5,000 GEL?') give clear usage context. The 'Indicative only: nothing is exchanged' caveat also clarifies when not to treat this as a transaction, but no alternative tool is named for rate-only or hours/limits queries.

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