Skip to main content
Glama

banking-intelligence

by ai.ohmyfin
OverviewDiscussionsAdmin

Bank Holidays

bank_holidays
Read-only

Get bank/public holidays for a country with payment impact analysis.

Returns all public holidays plus a 'payment_impact' section that shows:

  • Whether today is a business day or holiday in this country

  • Upcoming holidays in the next 14 days

  • Recent holidays in the last 14 days — for diagnosing a payment that is ALREADY stuck ("in progress for N days", "sent X days ago"). A recent holiday only counts if BOTH hold: it falls INSIDE the payment's own window (on or after the send date), AND its 'costs_a_business_day' is true. One that predates the send date is irrelevant, and one on the country's banking weekend closed nothing that was open — neither may be subtracted or given to the user as a cause. An empty list affirmatively means no recent holiday explains the delay — do not invent one from training data.

  • Every holiday entry (upcoming, recent, and next_holiday_after_today) carries 'costs_a_business_day'. Roughly one holiday date in six lands on its own country's weekend and shortens nothing; check the flag before quoting a holiday as a delay, a closure or a reason a window was short.

  • elapsed_business_days_by_send_date — the AUTHORITATIVE elapsed business-day count keyed by send date (weekends + this country's holidays already excluded). Use it verbatim instead of hand-counting.

  • Next business day and how many consecutive non-business days remain This context helps determine if holidays are causing payment delays.

Examples: bank_holidays("US") bank_holidays("DE", 2026) bank_holidays("GB", 2025)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoCalendar year, 2020-2030 (default: the current year). Values outside the range are clamped.
country_codeYesISO 3166-1 alpha-2 country code, e.g. "US", "DE", "GB".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / country_code / description
      Added value: +"ISO 3166-1 alpha-2 country code, e.g. \"US\", \"DE\", \"GB\"."
    • addedInput schema / properties / year / description
      Added value: +"Calendar year, 2020-2030 (default: the current year). Values outside the range are clamped."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint, yet the description discloses a great deal beyond that: the payment_impact section shape, the two-part rule for a recent holiday counting, the meaning of an empty list, the costs_a_business_day flag caveat, and that elapsed_business_days_by_send_date is authoritative. This is unusually rich behavioral context.

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?

The purpose is front-loaded and the bulleted return-value breakdown keeps a long description scannable. The length is largely earned by the payment-delay diagnostic rules, though a few clauses (e.g. repeated warnings about inventing holidays) could be tightened.

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?

For a two-parameter lookup whose output schema already exists, the description supplies everything an agent needs to interpret and safely act on the result, including how to reason about holiday-caused delays and the authoritative business-day count.

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 description coverage is 100%, so both country_code and the year range/clamping behavior are already documented in the schema. The examples (bank_holidays("US"), bank_holidays("DE", 2026)) only illustrate call shape and add no semantics beyond the schema, so the baseline 3 applies.

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 opening sentence states a specific verb and resource ('Get bank/public holidays for a country') and adds the differentiating scope ('with payment impact analysis'), which separates it from siblings like is_business_day_check and value_date.

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 frames the use case: diagnosing a payment that is ALREADY stuck, plus checking whether today is a business day and upcoming/recent holidays. Strong context, but it never names the alternative sibling tools an agent should prefer for the narrower business-day or value-date questions.

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

All banking-intelligence toolsInspect
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