Conecto

Convert amounts between currencies

valuation_fx

Read-onlyIdempotent

Amounts converted at the ECB's euro reference rates: on a date (the latest rates published on or before it; none come out on weekends and TARGET holidays), or at a past year's average, for a year's figures like revenue. Peers and targets that report in different currencies are compared in one currency: convert their figures before valuation_multiples or valuation_benchmark. Today's rates when neither date nor year is given. Free.

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": {
      "amounts": "<amounts>",
      "to": "<to>"
    },
    "name": "valuation_fx"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	The currency to convert into, e.g. EUR.
`date`	No	Rates on this day.
`year`	No	A past year's average.
`amounts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description's value is the added context it provides: the ECB as data source, the on-or-before fallback rule, that no rates publish on weekends or TARGET holidays, and that the tool is free. It omits output shape and rounding/precision behavior, which matters for a currency conversion, keeping it below a 5.

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?

It is front-loaded and dense with no filler, but the prose is telegraphic and fragmentary ('Today's rates when neither date nor year is given. Free.'), which reads as clipped notes rather than a structured sentence flow. Every clause does carry information, so no real waste.

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 read-only 4-parameter tool with no output schema, the description covers source, timing semantics, default resolution, and downstream usage — enough to call correctly. It leaves unstated what the returned array contains (labels, converted values, the rate applied) and how precision is handled, which would matter for chained valuation work.

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 coverage is 75%, so the schema already documents 'to', 'date', 'year' and nested currency codes. The description adds meaning the schema lacks: 'date' resolves to the latest rates published on or before it (with weekend/holiday gaps), 'year' selects a past year's average intended for annual figures, and the pair is implicitly either/or with today as default.

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 opening clause states a specific verb and resource ('Amounts converted at the ECB's euro reference rates') and immediately scopes it to euro-based reference rates, which distinguishes it from the sibling valuation_rates (rate lookup) and from the downstream multiples/benchmark tools. An agent can tell what this tool does and does not do without opening the schema.

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?

It names the concrete workflow ('convert their figures before valuation_multiples or valuation_benchmark') and states the default when neither date nor year is supplied. It does not explicitly say when to use valuation_rates instead of this tool for raw rate retrieval, so the exclusion is only implied.

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

All Conecto 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.

Resources

Need Help?