Folionomiq

What exchange rates did to it

currency_effect

Read-onlyIdempotent

For a portfolio held in one currency but priced partly in others: how much is outside the base currency, and what exchange rates added to growth, volatility and the worst fall, against the same holdings currency-hedged. Typical questions: 'I'm in euros but hold US funds: what did the dollar do to me?'; 'How much currency risk is in this?'; 'Hedged or not, what was the difference?'. Limits: Only when some holdings are priced in another currency than the holder's. base must be set to the holder's currency. It does not recommend, predict or calculate tax.

Input Schema

Name	Required	Description
`base`	No	Currency code every figure is expressed in: USD, EUR, GBP, CAD… Default USD.
`units`	No	What the holdings' numbers are: 'money' (amounts in the base currency) or 'weights' (percentages or fractions). Omitted: holdings adding up to 1 or 100 are read as percentages, anything else as money, and the answer says so.
`holdings`	Yes	What is held: {ticker: number}, 1 to 100 holdings. Weights in any scale (60/20/20 or 0.6/0.2/0.2) or money amounts in the base currency (60000/20000/20000): `units` says which; without it, holdings adding up to 1 or 100 are read as percentages, anything else as money, which makes the falls come out in money. Tickers as the exchange lists them (VOO, VWCE.DE, EQQQ.DE, XAW.TO; 'CASH.USD' for cash). Example: {"VTI": 60, "VXUS": 20, "BND": 20}.

Output Schema

Name	Required	Description
`base`	No	Base currency.
`data`	No	Where the prices came from and what was missing or repaired.
`_fence`	Yes	What these figures are and are not: descriptive, no forecast, no advice. Repeat its sense when presenting the result.
`hedged`	No	The same with the currency moves removed.
`headline`	No	One sentence summary.
`unhedged`	No	Growth, volatility and worst fall as held.
`by_currency`	No	[currency, share of the money] pairs, by listing currency.
`limitations`	No	What this cannot show (listing currency is not earning currency).
`share_of_vol`	No	Share of the volatility that comes from exchange rates.
`foreign_share`	No	Share of the money priced outside the base currency.
`cagr_from_currency`	No	Growth per year added (or removed) by exchange rates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / holdings / description

Previous value: -"What is held: {ticker: number}, 1 to 100 holdings. Weights in any scale (60/20/20 or 0.6/0.2/0.2) or money amounts in the base currency (60000/20000/20000): holdings adding up to 1 or 100 are read as percentages, anything else as money, which makes the falls come out in money. Tickers as the exchange lists them (VOO, VWCE.DE, EQQQ.DE, XAW.TO; 'CASH.USD' for cash). Example: {\"VTI\": 60, \"VXUS\": 20, \"BND\": 20}."New value: +"What is held: {ticker: number}, 1 to 100 holdings. Weights in any scale (60/20/20 or 0.6/0.2/0.2) or money amounts in the base currency (60000/20000/20000): `units` says which; without it, holdings adding up to 1 or 100 are read as percentages, anything else as money, which makes the falls come out in money. Tickers as the exchange lists them (VOO, VWCE.DE, EQQQ.DE, XAW.TO; 'CASH.USD' for cash). Example: {\"VTI\": 60, \"VXUS\": 20, \"BND\": 20}."

addedInput schema / properties / units

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "money",
+        "weights"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "What the holdings' numbers are: 'money' (amounts in the base currency) or 'weights' (percentages or fractions). Omitted: holdings adding up to 1 or 100 are read as percentages, anything else as money, and the answer says so.",
+  "title": "Units"
+}

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / base / description

Previous value: -"Currency every figure is expressed in (USD, EUR, GBP, CAD…). Default USD."New value: +"Currency code every figure is expressed in: USD, EUR, GBP, CAD… Default USD."

changedInput schema / properties / holdings / description

Previous value: -"What is held: {ticker: weight or amount}. Weights need not sum to one; amounts in the base currency are also accepted (then the crises are shown in money). 1 to 100 holdings. Tickers as the exchange lists them (VOO, VWCE.DE, XAW.TO; 'CASH.USD' for cash)."New value: +"What is held: {ticker: number}, 1 to 100 holdings. Weights in any scale (60/20/20 or 0.6/0.2/0.2) or money amounts in the base currency (60000/20000/20000): holdings adding up to 1 or 100 are read as percentages, anything else as money, which makes the falls come out in money. Tickers as the exchange lists them (VOO, VWCE.DE, EQQQ.DE, XAW.TO; 'CASH.USD' for cash). Example: {\"VTI\": 60, \"VXUS\": 20, \"BND\": 20}."

AddedSep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the readOnlyHint/idempotent annotations, it discloses that the tool does not recommend, predict or calculate tax, and that base must match the holder's currency. It does not describe return format or error behavior, but with an output schema and strong annotations, this adds useful context.

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 description is front-loaded with the core purpose, then typical questions, then limits. It is appropriately sized, though the illustrative questions could be seen as slightly verbose; every part still adds clarity.

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?

Given the tool's complexity (nested holdings, currency mismatch, hedged comparison) and the presence of a full output schema and annotations, the description is complete enough for an agent to decide when and how to call it correctly.

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 100%, so the baseline is 3. The description adds a meaningful constraint not in the schema: base must be set to the holder's currency. It otherwise relies on the schema for units and holdings format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific analytical purpose: decomposing currency effects on growth, volatility and worst fall for holdings partly outside the base currency, and comparing against a hedged version. It is clear what the tool does, but does not explicitly differentiate itself from sibling portfolio analysis 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?

It provides concrete typical questions ('I'm in euros but hold US funds...') and a clear limit: only applies when some holdings are priced in another currency, and base must be the holder's currency. However, no alternative tools are named for cases where the limit is not met.

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

All Folionomiq 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?