convert_currencyConvert an amount between any two supported currencies (crypto or fiat). Uses the direct pair when available, otherwise bridges through USD/USDT/UAH/EUR.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Target currency symbol, e.g. UAH or EUR | |
| from | Yes | Source currency symbol, e.g. BTC or USD | |
| amount | No | Amount to convert. Defaults to 1. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Missing details on supported currencies list, rate freshness, fees, or output format. Annotations empty, so description carries full burden but only mentions bridging strategy.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences with no unnecessary words, front-loaded with the main action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple conversion tool given schema coverage, but missing supported currency list and output description. No output schema to compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions cover all parameters (100%). Description does not add meaning beyond schema, so baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it converts between two currencies, specifies crypto or fiat, and distinguishes from siblings (get_latest_rates, get_rate_history, get_service_status).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides bridging strategy context but lacks explicit when-to-use or when-not-to-use guidance compared to siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct purpose: conversion, current rates, historical rates, and service status. There is no overlap in functionality.
All tools follow a consistent verb_noun pattern using lowercase and underscores, making them predictable and easy to understand.
With 4 tools, the server is well-scoped for a price feed service, covering essential operations without unnecessary bloat.
The tool set covers key operations: conversion, current rates, historical data, and service status. No obvious gaps for the stated domain.