Skip to main content
Glama

PlugRail Japanese Calendar

by dev.plugrail

business_days_between

from〜to間の営業日数を数えます。既定では「fromを含まず、toを含む」境界です（例:「今日から支払期日まで何営業日か」）。include_from/include_toで境界を変更できます。土日・日本の祝日を除外し、calendar="banking"を指定すると銀行休業日（12/31〜1/3）も除外します。from > to の場合はエラーにせず、from/toとinclude_from/include_toを入れ替えて計算した結果の符号を反転した値（負の営業日数）を返します（反対称則: count(A,B,x,y) = -count(B,A,y,x)。A≠B、すなわちfrom≠toの場合に成立する恒等式で、from===toはこの分岐に入らないため対象外）。入力例: {"from": "2026-07-10", "to": "2026-07-20"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes終点日 YYYY-MM-DD。例: "2026-07-20"。fromより前の日付も指定可（結果は負の営業日数になります）。
fromYes起点日 YYYY-MM-DD。例: "2026-07-10"。
calendarNo"standard"（既定）または"banking"（銀行休業日も除外）。
include_toNotoを営業日数に含めるか。既定はtrue。
include_fromNofromを営業日数に含めるか。既定はfalse。
extra_closed_datesNo顧客固有の追加休業日（YYYY-MM-DD の配列）。例: ["2026-12-29", "2026-12-30"]

TDQS

A4.3/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It thoroughly discloses default boundary semantics (from excluded, to included), weekend/holiday exclusion, optional banking calendar, and the antisymmetry behavior when from > to, including a formula and its applicability condition. This is rich, non-obvious 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 description is somewhat long but each sentence contributes essential information: purpose, boundary defaults, calendar options, and edge-case behavior. It is well-structured with a clear lead, though the antisymmetry formula could be seen as slightly over-detailed for a general audience.

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?

For a tool with 6 parameters, no output schema, and no annotations, the description covers all key aspects: purpose, default behavior, configuration, edge cases, and an example. It does not explicitly state return type or invalid-date behavior, but these are minor gaps given the tool's scope.

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?

The input schema has 100% coverage, describing each parameter individually. The description adds global context (default boundary, reversal behavior) but does not significantly enhance meaning for individual parameters beyond what the schema already provides. The baseline 3 is appropriate given high schema coverage.

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 counts business days between two dates, using a specific verb ('数えます') and resource ('from〜to間の営業日数'). It distinguishes from siblings by focusing on counting rather than adding, checking, or listing holidays, and includes boundary and reversal details.

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?

The description provides a concrete use case ('今日から支払期日まで何営業日か') and explains configuration options (include_from/include_to, calendar). It does not explicitly name alternatives or state when not to use it, but the purpose is clear enough that an agent can infer appropriate usage.

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

All PlugRail Japanese Calendar toolsInspect
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.5/5.0
Disambiguation5/5

Each tool has a distinct purpose: adding business days, counting between dates, checking holiday status, and listing holidays. No overlap or ambiguity.

Naming Consistency5/5

All tool names use snake_case with a consistent verb_noun or is_ pattern (add_business_days, business_days_between, is_holiday, list_holidays).

Tool Count5/5

4 tools is appropriate for a calendar/holiday server, covering the essential operations without being too sparse or overloaded.

Completeness5/5

The tool set covers core business day arithmetic (add, count) and holiday information (check, list). Negative days and calendar options are included, so no obvious gaps.

Resources