CurrencyGuard Guard Pricing

Get Forward FX Rate

get_forward_rate

Read-only

Use when you need a forward FX rate. tenor accepts either a period such as 1W, 1M, 3M, 6M, 1Y, or an exact date in ISO form YYYY-MM-DD. Use an exact date whenever you need the forward for the same day a Guard settles: a period resolves to the forward curve's own date, which can be several days away, and a comparison across two different dates is misleading. Rates are taken from the market forward curve, rounded, and for illustration purposes only — not for execution. Returns: forwardRate (indicative mid outright rate for that date), spotMid (indicative spot mid rate for comparison), settlementDate (the date the rate is for). A forwardRate below spotMid means the forward is cheaper than spot for the base currency; above means dearer. Example: base=GBP, quote=USD, tenor=2026-12-29 returns the GBPUSD forward for that day.

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": {
      "base": "<base>",
      "quote": "<quote>",
      "tenor": "<tenor>"
    },
    "name": "get_forward_rate"
  }
}

Input Schema

Name	Required	Description
`base`	Yes	Base currency ISO code, e.g. GBP
`quote`	Yes	Quote currency ISO code, e.g. USD
`tenor`	Yes	Tenor period such as 1W, 1M, 3M, 6M, 1Y, or an exact date as YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 16, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / base / maxLength
```
Added value: +3
```
- addedInput schema / properties / base / minLength
```
Added value: +3
```
- addedInput schema / properties / quote / maxLength
```
Added value: +3
```
- addedInput schema / properties / quote / minLength
```
Added value: +3
```
- changedInput schema / properties / tenor / description
```
Previous value: -"Tenor period, e.g. 1W, 1M, 3M, 6M, 1Y"New value: +"Tenor period such as 1W, 1M, 3M, 6M, 1Y, or an exact date as YYYY-MM-DD"
```
Changed1 schema field changedMay 11, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedApr 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/non-destructive annotations, it discloses that rates come from the market forward curve, are rounded, and are indicative only — not executable. It also explains the semantic relationship between forwardRate and spotMid, which is genuine behavioral context an agent cannot infer elsewhere.

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?

Front-loaded with the trigger condition, then the tenor rules, then the return semantics. Every sentence carries information, though the interpretation sentence about forwardRate vs spotMid and the example make it denser than strictly necessary.

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?

No output schema exists, yet the description enumerates the three return fields (forwardRate, spotMid, settlementDate) and how to read them. Combined with the tenor caveat and the indicative-only disclaimer, nothing an agent needs to call or interpret this tool correctly is missing.

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 already 100%, but the description adds meaning the schema lacks: the period-vs-exact-date resolution semantics and a worked example (base=GBP, quote=USD, tenor=2026-12-29). This is real added value over the schema's flat enumeration of tenor formats.

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?

States a specific verb and resource ('get a forward FX rate') and implicitly separates itself from get_spot_rate by explaining that spotMid is returned only as a comparison. An agent can identify the tool's function 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?

Gives concrete when-to-use guidance for the tenor argument, including the rule to prefer an exact ISO date when matching a Guard settlement and the warning that period-based dates can drift by several days. It does not explicitly name sibling tools such as get_spot_rate or resolve_settlement_date as alternatives, which keeps it short of a 5.

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

All CurrencyGuard Guard Pricing 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?