ZapifyAPI MCP Server

convert_currency

Convert between currencies using live exchange rates. Enter source and target currency codes and optionally an amount to get the converted value.

Instructions

Convert between currencies with real-time exchange rates.

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

Input Schema

Name	Required	Description
`to`	Yes
`from`	Yes	Currency code (USD, EUR, etc)
`amount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full disclosure burden. It mentions 'real-time exchange rates' but does not clarify whether the operation is read-only, how errors are handled, or what data source is used. This is a notable gap for a simple converter.

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?

The description is a single sentence of six words, with no redundancy. It front-loads the purpose and is appropriately sized for a simple conversion tool.

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

Completeness2/5

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

With no annotations, no output schema, and low parameter coverage, the description is too sparse to fully guide an agent. It does not state what the result is (e.g., the converted amount) or how the 'amount' parameter is interpreted, leaving important context missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only 'from' is described). The description does not help explain the 'to' or 'amount' parameters, their formats, or how they relate to the conversion. It adds minimal value beyond the schema.

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?

The description uses a specific verb 'convert' with the resource 'currencies', clearly distinguishing it from sibling tools like convert_units and convert_timezone. The phrase 'real-time exchange rates' adds a specific and accurate scope.

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?

The description implies the tool is for currency conversion, but it does not explicitly state when to use it over alternatives or provide exclusions. The context of sibling tools makes the intended use somewhat clear, but the description itself offers no direct guidance.

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