CurrencyGuard Guard Pricing

Resolve Settlement Date

resolve_settlement_date

Read-only

Resolve a relative time period (tenor) to a valid business settlement date for a currency pair. Use this when a user says '3 months', '6 months', '1 year', etc. instead of an exact date. The tenor format is: 1D (days), 1W (weeks), 1M (months), 1Y (years). Examples: '3M' = 3 months, '6M' = 6 months, '1Y' = 1 year. The returned date accounts for weekends and public holidays in both currencies' financial centres. Use the returned settlementDate as the exact date parameter for price_guard.

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": {
      "currencyPair": "<currencyPair>",
      "tenor": "<tenor>"
    },
    "name": "resolve_settlement_date"
  }
}

Input Schema

Name	Required	Description	Default
`tenor`	Yes	Tenor string, e.g. 3M, 6M, 1Y
`currencyPair`	Yes	Currency pair, e.g. GBPUSD

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026
- addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
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 already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. Beyond that the description adds real behavioral context: the result is holiday- and weekend-adjusted across both currencies' financial centres, and the returned settlementDate is meant to be reused as price_guard's exact date parameter.

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 core purpose and the usage trigger, and the closing sentence about price_guard is valuable operational guidance. The tenor example list ('3M = 3 months, 6M = 6 months, 1Y = 1 year') is redundant after the format spec and could be trimmed.

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?

For a two-parameter, read-only tool with no output schema, the description covers the essentials: input format, holiday/weekend adjustment logic, and the field name returned (settlementDate). It does not mention error behavior for unsupported tenors or currency pairs, but nothing critical is missing for correct invocation.

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% and both parameters are already documented, so the baseline is 3. The description does add the tenor unit grammar (1D/1W/1M/1Y), which goes beyond the schema's brief examples, but the illustrative mappings ('3M = 3 months') largely restate the obvious and no extra meaning is given for currencyPair.

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 ('Resolve a relative time period (tenor) to a valid business settlement date') plus scope (for a currency pair). This is clearly distinct from siblings like get_spot_rate or price_guard, and the description makes the relationship to price_guard explicit.

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 condition ('when a user says 3 months, 6 months, 1 year instead of an exact date') and a clear downstream instruction to feed settlementDate into price_guard. It lacks an explicit when-not-to-use or a named alternative for cases where an exact date is already known, so it falls short of a full 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?