Skip to main content
Glama

Compute day count to settlement

compute-day-count-to-settlement
Read-onlyIdempotent

Use when you need a Canadian settlement date or accrual fraction. Rolls a trade date forward on the Payments Canada calendar and counts the accrual under ACT/360, ACT/365F, 30/360, 30E/360 or ACT/ACT-ISDA. $0.01 USDC on Base per answer via x402; a refusal is free.

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": {
      "accrual_start": "<accrual_start>",
      "trade_date": "<trade_date>",
      "settlement_lag": "<settlement_lag>",
      "calendar": "<calendar>",
      "convention": "<convention>",
      "acknowledge": "<acknowledge>",
      "freshness_tolerance": "<freshness_tolerance>"
    },
    "name": "compute-day-count-to-settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendarYes
conventionYes
trade_dateYesa business day on the calendar
acknowledgeYes
accrual_startYesa real calendar date, the first day of the accrual period, counted
settlement_lagYes
freshness_toleranceYesat most the ratified ceiling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds genuinely distinctive behavior: this is a paid x402 endpoint at $0.01 USDC on Base per answer, with refusals free. That pricing and refusal semantics are invisible in the structured data and materially affect whether an agent calls it. It does not explain what a "refusal" is or how the x402 payment is actually executed in-session, leaving a gap.

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?

Three sentences, front-loaded with the trigger condition and followed by mechanism and cost. Every clause carries information an agent needs before calling; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-required-parameter tool with no output schema, the description should at least characterize the returned settlement date and accrual fraction's shape, and it only names them in passing. The acknowledge and freshness_tolerance parameters remain unexplained alongside a nontrivial payment flow, so an agent could invoke this correctly only by guessing at three inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 43%, so the description must carry the undocumented parameters, and it does not. It restates the convention enum and the Canada calendar already in the schema, but never explains settlement_lag (0-5 business days?), the opaque required acknowledge="no-ruling-v1" flag, or freshness_tolerance's cryptic "at most the ratified ceiling".

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 concrete verbs and resources: rolls a trade date forward on the Payments Canada calendar and computes accrual under five named conventions. The domain (Canadian settlement / accrual fraction) is unambiguous and cannot be confused with the sibling tools, which do timestamp, base64, and diff work.

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?

"Use when you need a Canadian settlement date or accrual fraction" gives an explicit triggering condition, which is the right shape for a single-purpose tool. It stops short of when-not guidance (e.g. non-Canadian calendars, unsupported conventions), but the sibling set is unrelated enough that no routing caution is needed.

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.

Resources