nestegg-calculators

FX Convert

fx-convert

Read-onlyIdempotent

Convert an amount using a rate supplied by the caller (units of target currency per unit of source). No rate is ever looked up.

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>",
      "rate": "<rate>"
    },
    "name": "fx-convert"
  }
}

Input Schema

Name	Required	Description	Default
`rate`	Yes	Rate: target units per source unit.
`amount`	Yes	Amount to convert.

Output Schema

Name	Required	Description	Default
`value`	No	Result value.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds valuable behavioral context by stating that the rate is supplied by the caller and that no rate lookup is performed. This goes beyond the annotations to clarify the tool's pure calculation nature.

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 two concise sentences with no redundant wording. It is front-loaded with the action ('Convert an amount') and efficiently communicates the key scope constraint ('No rate is ever looked up').

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?

The tool is simple with only two parameters, both fully documented in the schema, and an output schema is present. The description, combined with annotations and schema, provides complete context for correct usage. No additional details like rounding or edge cases are necessary for this straightforward calculation tool.

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 schema already provides 100% parameter description coverage, so the baseline is 3. The description restates the rate unit meaning ('units of target currency per unit of source') which is already in the schema's rate description, adding no new semantic information beyond what the schema provides.

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 clearly states the tool converts an amount using a caller-supplied rate, which is a specific verb+resource. It distinguishes itself from siblings by emphasizing that no rate lookup occurs, which is unique among the financial calculation tools.

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 clearly implies when to use this tool: when you have a rate and want to convert. The phrase 'No rate is ever looked up' provides an exclusionary guideline, signaling that this tool is not for rate retrieval. However, it does not explicitly name alternatives or provide explicit when-not-to-use conditions.

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

All nestegg-calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.