reference-data

settlement_date

PAID ($0.05). Settlement/value date: the date n business days after a trade date, computed on the INTERSECTION of the calendars you name, with a per-day trail showing every skipped day and why, on which calendar. Supply business_days for a cycle you are trading under, or market + instrument_class to have a settlement cycle applied that we cite to its primary source (e.g. US equities T+1 under 17 CFR 240.15c6-1(a); UK gilts T+1 by DMO convention, which is NOT the T+2 equity cycle; Japan equities T+2 but JGBs T+1). Calendars are NATIONAL statutory holiday calendars with researched statutory weekend rules (Israel Saturday-only, Gulf Friday+Saturday, India Sundays plus the 2nd and 4th Saturday), NOT CSD or exchange calendars — each response states the basis and any known divergence. Use 'eu.t2' for the euro cash leg. We refuse FREE rather than guess: beyond published calendar coverage, no cited cycle for the instrument (government bonds never inherit an equity cycle), a cycle not in force on the trade date, or FX spot value dates. Free companion: GET /settlement-conventions.

Input Schema

TableJSON Schema

Name	Required	Description
`market`	No	ISO country of the market whose cited cycle should apply (with instrument_class)
`api_key`	No	API key (bypasses x402; metered for invoicing)
`calendars`	Yes	Calendar ids to intersect: two-letter ISO country codes, plus 'eu.t2' for the euro cash leg
`trade_date`	Yes	Trade/reference date, YYYY-MM-DD. Day 0: never counted, never rolled.
`business_days`	No	The offset you are trading under (T+n)
`instrument_class`	No	Instrument class — a government bond never inherits an equity cycle

TDQS

A4.9/5.0

Behavior5/5

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

No annotations provided, so description must fully disclose behavior. It does so comprehensively: paid ($0.05), refusal policy, calendar types (statutory holiday calendars, not exchange calendars), cycle sourcing, and the per-day trail output. 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.

Conciseness4/5

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

Description is long but each sentence adds value. Front-loaded with key purpose and cost. Some minor redundancy (e.g., 'PAID ($0.05)' appears first but not in a separate line). Still, highly efficient given the tool's complexity.

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

Completeness5/5

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

No output schema, but description implies the per-day trail format. Addresses edge cases: refusal rather than guess, documented citation sources, calendar types, and FX spot value dates. For a complex tool with 6 parameters, this is remarkably complete.

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

Parameters5/5

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

Schema coverage is 100%, but description vastly enriches parameter meaning. It explains the dual mode (business_days vs market+instrument_class), clarifies calendar IDs as ISO country codes plus 'eu.t2', and adds crucial context about inheritance rules (e.g., government bonds never inherit equity cycle). Far exceeds baseline.

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 specifies exactly what the tool computes: settlement/value date based on n business days after trade date, with clear distinction from siblings. It mentions paid nature, calendar intersection, and per-day trail. This is a specific verb+resource definition.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use business_days vs market+instrument_class, which calendars to use, and what scenarios lead to refusal. Mentions free companion endpoint. While it doesn't explicitly name sibling tools, it effectively tells when to use this tool instead of guessing or using other holiday/date tools.

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

All reference-data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clear, distinct purposes: minimum wage checking, income tax, VAT, working days, holidays, settlement dates, and generic series access all serve different functions. However, compute_vat and check_minimum_wage could be confused with simple get_series lookups for the same series (vat, minimum-wage), though the descriptions clarify that the compute_* tools provide breakdowns rather than just current values.

Naming Consistency4/5

The majority of tools follow a consistent verb_noun snake_case pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). Settlement_date breaks the pattern as a noun-only name instead of something like get_settlement_date, creating a minor deviation.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose. It covers a broad but justified range of statutory and financial reference data without being excessive, and each tool serves a distinct function within that domain.

Completeness5/5

The tool set provides comprehensive coverage of typical reference data: minimum wage, income tax, VAT, public holidays, working days, settlement dates, and generic series with current values, history, and snapshots. The inclusion of list_series for discovery and the generic get_series/get_series_history endpoints cover the full lifecycle of accessing reference data. No obvious gaps for the stated purpose.

Resources

Need Help?