Skip to main content
Glama

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tenorYesTenor string, e.g. 3M, 6M, 1Y
currencyPairYesCurrency pair, e.g. GBPUSD

TDQS

A4.4/5.0
Behavior4/5

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

Description explains the return value accounts for weekends/holidays; annotations indicate read-only and non-destructive, with no contradictions.

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

Conciseness5/5

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

Concise sentences with front-loaded purpose, examples, and usage instruction; no wasted words.

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?

Describes return value (settlement date with holiday adjustment) and directs to price_guard; despite no output schema, it is adequate for the task.

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?

Adds meaning beyond schema by explaining tenor format with examples and currency pair format; schema coverage is 100%.

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 resolves a relative time period to a business settlement date for a currency pair, with examples distinguishing it from siblings like price_guard.

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 says when to use (when user gives relative time like '3 months') and directs to use output for price_guard, but lacks explicit when not to use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a distinct purpose: explanation, rate queries (spot, forward, historic), supported currencies, pricing, extension pricing, and date resolution. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., explain_guard_product, get_forward_rate). Verbs are descriptive and uniform.

Tool Count5/5

8 tools cover the core functionality of pricing and explaining a currency hedging product without being excessive or insufficient. Each tool serves a clear purpose.

Completeness5/5

The tool set covers explanation, rate information (spot, forward, historic), supported currencies, initial pricing, extension pricing, and date resolution – a complete workflow for quoting and understanding the Guard product.

Resources