CurrencyGuard Guard Pricing

Price Guard Extension

price_guard_extension

Read-only

Get an indicative price for extending a Guard to a later settlement date. Use it when a customer asks what it costs to extend a Guard. Returns: extensionCost, what the customer pays to extend, in the home currency. Show it as the answer: "Extending to [date] costs [extensionCost]". It is one figure; there is no breakdown. Also the currencies, the direction, the foreign amount, both dates, valid, errors, stale. Both dates are moved to the next business day when needed, and a note says so. Parameters: guardCurrency, foreignCurrency, payReceive, foreignAmount, originalSettlementDate, extendedSettlementDate. There is no Guard rate input: the server prices the extension at today's market rate, not at the rate of the Guard the customer holds. Say that the figure is indicative for that reason too.

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": {
      "guardCurrency": "<guardCurrency>",
      "foreignCurrency": "<foreignCurrency>",
      "payReceive": "<payReceive>",
      "foreignAmount": "<foreignAmount>",
      "originalSettlementDate": "<originalSettlementDate>",
      "extendedSettlementDate": "<extendedSettlementDate>"
    },
    "name": "price_guard_extension"
  }
}

Input 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.4/5.0

Behavior5/5

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

Annotations already mark it read-only and closed-world, yet the description adds substantial context: pricing occurs at today's market rate rather than the held Guard's rate, there is no Guard rate input, dates may roll to the next business day with a note, and the result is a single indicative figure with no breakdown. These are behavioral traits the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and usage are front-loaded, but the middle degrades into a loose fragment ('Also the currencies, the direction, the foreign amount, both dates, valid, errors, stale') that reads as a field dump rather than a sentence. The closing caveat is repeated in slightly different words ('indicative ... for that reason too'), costing space.

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?

There is no output schema, so the description carries the return-value burden and does enumerate the response fields (extensionCost plus currencies, direction, amount, dates, valid, errors, stale) along with a suggested presentation format. The enumeration is disorganized, but an agent has enough to interpret and relay the result.

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, but the description adds real value by listing all six inputs and explicitly stating that no Guard rate parameter exists and why — pre-empting an agent's attempt to supply one. It also explains the business-day roll applied to both date parameters.

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') with clear scope, which cleanly separates it from price_guard and get_forward_rate in the sibling list. An agent can identify the operation 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 an explicit trigger: 'Use it when a customer asks what it costs to extend a Guard.' That is clear context for invocation, but no when-not conditions or named alternatives (e.g., price_guard for a new Guard) are offered.

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?