Skip to main content
Glama
tresor4k

macalc

calculate_currency_cross_rate

Calculate cross exchange rate between two currencies using their USD rates. Provide units of currency A per USD and currency B per USD to get cross rates A/B and B/A.

Instructions

Calculate cross exchange rate between two currencies via USD. Returns: {cross_rate_a_to_b, cross_rate_b_to_a}. See list_bundles for related 'conversions' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rate_a_usdYesUnits of currency A per 1 USD
rate_b_usdYesUnits of currency B per 1 USD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations exist, so description carries the burden. It discloses the calculation method (via USD) and return structure, but doesn't mention behavioral traits like read-only, idempotency, or side effects. Adequate but minimal.

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?

Two concise sentences with front-loaded action and no wasted words. Efficiently conveys purpose and output.

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 simple calculation tool with output schema, the description covers purpose, method, and output. Could mention that both cross rates are returned, but overall complete given sibling count and available structured data.

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?

Input schema has 100% coverage with descriptions. The description adds context ('via USD') that reinforces the schema but does not provide additional parameter details beyond what schema already offers.

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?

Description clearly states the tool calculates cross exchange rate between two currencies via USD, and specifies the return format. It distinguishes itself by mentioning the 'via USD' method and referring to related calculators.

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?

No explicit guidance on when to use this tool versus alternatives like calculate_currency_exchange. The mention of list_bundles for related calculators implies a category but lacks specific when/when-not context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server