Skip to main content
Glama

fx_exposure

Quantify currency risk on USD ocean-freight spend paid in your home currency. Calculates exposure, volatility, 95% adverse FX move, and hedge ratio based on your risk tolerance.

Instructions

Quantify and hedge the CURRENCY RISK of your ocean-freight spend. Freight is quoted and largely invoiced in USD, but a non-US shipper PAYS in its home currency (EUR/GBP/JPY/CNY/…) — so a large, recurring USD freight bill is a foreign-exchange exposure: if the home currency weakens, the same freight costs more locally. Pass your home currency + your annual USD freight spend, and it returns: the exposure in your local currency at a modeled spot, the annualised VOLATILITY band of the pair, the 95% adverse FX move on the spend (in money), and a HEDGE-RATIO recommendation — what % of the exposure to cover with forwards — using a media-variance objective analogous to the procurement engine: higher volatility and a lower risk tolerance push the hedge up, but a variable spend caps it (you can't lock forwards for volume you might not ship), so it never blindly recommends 100%. It also sketches the forward-points carry (so the hedge isn't assumed free) and a laddered hedging plan. Honest (regla 7): MODELED reference analysis, NOT live market quotes and NOT financial / hedging advice — consult a treasury/FX professional. PREMIUM: pay per call with x402 (USDC on Base) or a prepaid key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
local_currencyYesYour home currency you pay freight in: EUR, GBP, JPY, CNY, INR, KRW, CAD, AUD, SGD, BRL, MXN (or a name). REQUIRED.
annual_freight_spend_usdYesYour yearly USD ocean-freight bill (the USD exposure). REQUIRED.
horizon_monthsNoHedging horizon in months (1-36, default 12). The exposure & risk are pro-rated to it.
risk_toleranceNo'low' (hedge more), 'medium' (default) or 'high' (hedge less).
spend_cvNoRelative std-dev of your freight spend itself (e.g. 0.2 = ±20% volume). Caps the hedge ratio. Optional; default 0.15.
Behavior5/5

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

With no annotations, the description fully bears the transparency burden. It discloses that the tool provides modeled estimates (not live), details the calculations (volatility, 95% adverse move, hedge ratio using media-variance), and states it does not give financial advice. It also mentions premium cost.

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 well-structured: purpose first, then explanation, outputs, caveats, and cost. It is front-loaded and informative, though somewhat verbose with phrases like 'Honest (regla 7)' that could be trimmed without losing value.

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, no output schema, and no annotations, the description is thorough. It explains all return values (exposure in local currency, volatility, 95% move, hedge ratio, forward points, laddered plan) and limitations, leaving no major gaps for an agent to understand its behavior.

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?

Schema coverage is 100%, so the baseline is 3. The description restates the purpose of parameters like local_currency and annual_freight_spend_usd but does not add significant new information beyond what the schema descriptions already provide.

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's purpose: 'Quantify and hedge the CURRENCY RISK of your ocean-freight spend.' It specifies inputs and outputs, and distinguishes itself from other tools by focusing on ocean-freight FX exposure, not live quotes or financial advice.

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 provides clear context on when to use: for non-US shippers with USD freight bills. It includes a caveat that it is a modeled reference analysis, not live quotes or advice, and advises consulting a professional. However, it lacks explicit comparison to sibling tools or a 'when not to use' section.

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/Baneado98/freight-pulse'

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