Skip to main content
Glama

Last business day of a month / 月末の最終営業日

last_business_day_of_month
Read-onlyIdempotent

Return the last business day of the given month. flags: estimated/unverified when the year's holidays are an estimate (tell the user). / その月の最終営業日を返します。その年の祝日が見込みのときは、flags に estimated・unverified が付きます(利用者に伝えてください)。

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": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "last_business_day_of_month"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (1980-2099) / 年
monthYesMonth (1-12) / 月
calendarNo"standard": weekends and national holidays are closed. "bank": also closed Dec 31 - Jan 3 (Japanese bank holidays). / standard:土日・祝日が休みです。bank:それに加えて、12月31日〜1月3日も休みです(銀行の休業日)standard
extra_holidaysNoAdditional company-specific closed days (e.g. summer break). / 会社独自の休みの日
extra_business_daysNoDays treated as business days even if they are weekends or holidays. / 休日でも営業日として扱う日

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / calendar / description
      Previous value: -"\"standard\": weekends and national holidays are closed. \"bank\": also closed Dec 31 - Jan 3 (Japanese bank holidays). / standard:土日・祝日が休み。bank:加えて12月31日〜1月3日が休み(銀行の休業日)"New value: +"\"standard\": weekends and national holidays are closed. \"bank\": also closed Dec 31 - Jan 3 (Japanese bank holidays). / standard:土日・祝日が休みです。bank:それに加えて、12月31日〜1月3日も休みです(銀行の休業日)"
    • changedInput schema / properties / extra_business_days / description
      Previous value: -"Days treated as business days even if they are weekends or holidays. / 休日でも営業日とする日"New value: +"Days treated as business days even if they are weekends or holidays. / 休日でも営業日として扱う日"
    • changedInput schema / properties / extra_holidays / description
      Previous value: -"Additional company-specific closed days (e.g. summer break). / 会社独自の休み"New value: +"Additional company-specific closed days (e.g. summer break). / 会社独自の休みの日"
  2. Changed1 schema field changed
    • addedInput schema / properties / calendar / maxLength
      Added value: +200
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety behavior is covered. The description adds one genuinely useful trait beyond them: a data-quality caveat that flags may be estimated/unverified and should be surfaced to the user. It does not describe the primary return value's form or how the holiday-estimate condition is determined.

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?

Two sentences, front-loaded with the purpose, with the caveat second. The bilingual duplication doubles the length but is necessary for the stated audience; nothing extraneous is present, though there is no structural separation of purpose from the flag instruction.

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?

With no output schema and five parameters, the description covers the core operation and one output caveat, which is adequate but leaves the return format implicit and says nothing about how extra_holidays and extra_business_days interact or override each other. For a computation tool whose correctness depends on those overrides, a bit more would help.

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 all five parameters, including the calendar enum and the extra_holidays/extra_business_days date arrays, are already documented in the schema. The description adds no parameter meaning beyond that, which is the baseline-3 case when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Return the last business day of the given month,' which is unambiguous about scope (single month, last business day). It does not explicitly contrast itself with siblings such as adjust_to_business_day or check_business_day, so it falls short of a 5, but the purpose is unmistakable.

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

Usage Guidelines3/5

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

There is no statement of when to use this tool versus the sibling business-day tools, and no exclusions or prerequisites. The only usage-like instruction is operational: when flags contain estimated/unverified, relay that to the user. That is implied guidance rather than routing guidance.

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