CurrencyGuard Guard Pricing

Price Guard Extension

price_guard_extension

Read-only

Get an indicative price for extending a Guard to a later settlement date. Estimates the additional cost using: (1) the guard fee difference between extended and original expiry, (2) the guard spread cost from the roll, and (3) the CurrencyGuard extension margin. Returns a breakdown: extensionCost = feeDifference + guardSpreadCost + extensionMargin. Both the original and extended quotes are priced at the same guard rate (the original quote's Guard rate), so the fee difference reflects purely the longer tenor, not market movement. Use this when a customer asks 'how much would it cost to extend my Guard by X months?' Parameters match price_guard plus the two dates.

Input Schema

TableJSON Schema

Name	Required	Description
`payReceive`	Yes	PAY if paying foreign currency, RECEIVE if receiving it
`foreignAmount`	Yes	Amount in foreign currency to protect
`guardCurrency`	Yes	Home/base currency ISO code, e.g. GBP
`foreignCurrency`	Yes	Foreign currency ISO code, e.g. USD
`extendedSettlementDate`	Yes	Extended (new) settlement date in ISO format YYYY-MM-DD
`originalSettlementDate`	Yes	Original settlement date in ISO format YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 16, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / foreignAmount / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / foreignCurrency / maxLength
```
Added value: +3
```
- addedInput schema / properties / foreignCurrency / minLength
```
Added value: +3
```
- addedInput schema / properties / guardCurrency / maxLength
```
Added value: +3
```
- addedInput schema / properties / guardCurrency / minLength
```
Added value: +3
```
- addedInput schema / properties / payReceive / enum
```
Added value: +[
+  "PAY",
+  "RECEIVE"
+]
```
Changed1 schema field changedMay 11, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations only declare readOnly/destructive hints, so the description adds real behavioral value: it discloses this is an indicative estimate, enumerates the cost components, and explains the pricing convention (both quotes use the original guard rate so the fee difference reflects tenor, not market movement). It doesn't state error/edge-case behavior such as an extended date earlier than the original.

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?

Purpose is front-loaded in the first sentence, and the formula breakdown plus the pricing-convention note both earn their place. It runs slightly long with five sentences, but none is filler.

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?

With no output schema, the description compensates by describing the return shape (extensionCost = feeDifference + guardSpreadCost + extensionMargin), and annotations carry the safety profile. It is complete enough to call correctly, though it omits failure conditions and any precision/currency caveats.

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 description coverage is 100%, so the baseline is 3. The description only says parameters mirror price_guard plus the two settlement dates, adding no syntax or format detail beyond what the schema already provides.

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 an indicative price for extending a Guard to a later settlement date') and scopes it precisely. It is clearly distinguishable from siblings like price_guard (which prices a new guard) and compare_guard_with_forward.

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?

Explicitly routes the agent with the customer-facing cue 'how much would it cost to extend my Guard by X months?' and anchors itself to a sibling ('Parameters match price_guard plus the two dates'). It lacks an explicit when-not or exclusions, but the context is clear.

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?