astrbot-mcp

convert_currency

Convert an amount from one currency to another using real-time exchange rates, with no API key required.

Instructions

按实时汇率换算货币（open.er-api.com，无需 API Key）。

Args: amount: 金额。 from_currency: 源货币代码，例如 USD、CNY、EUR。 to_currency: 目标货币代码，例如 JPY、GBP。

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_currency": "<from_currency>",
      "to_currency": "<to_currency>"
    },
    "name": "convert_currency"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes
`to_currency`	Yes
`from_currency`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the data source (open.er-api.com), that rates are real-time, and that no authentication is needed. It says nothing about failure modes such as invalid/unsupported currency codes, rate limits, or whether the amount must be positive.

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 core behavior is front-loaded in a single short sentence, followed by a compact arg list. The arg list is somewhat redundant with the schema field names but earns its place given zero schema description coverage.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the input parameters are all described. However, for a tool with no annotations and no schema descriptions, the definition leaves out validation rules and error behavior that an agent would need to call it reliably.

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?

Schema description coverage is 0%, so the description must compensate, and it does document all three parameters with meanings and concrete examples (USD, CNY, EUR; JPY, GBP). It stops short of stating code format constraints (ISO 4217, case sensitivity) or numeric bounds on amount.

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?

States a specific verb and resource ('换算货币' / convert currency) plus the rate source and the fact that no API key is required, which lets an agent identify the tool's exact function immediately. No sibling tool overlaps with currency conversion, so no differentiation is needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose statement; there is no explicit 'use this when…' guidance, no mention of what it cannot do (e.g. historical or offline rates), and no alternatives are named. The 'no API key needed' note is the only prerequisite-style context offered.

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