Skip to main content
Glama

Count working days between dates

business_days_between
Read-only

Counts South African working days between two dates (inclusive), excluding weekends and public holidays. Optionally counts Saturdays as working days. Useful for notice periods, payment terms and delivery dates.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "business_days_between"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesYYYY-MM-DD
startYesYYYY-MM-DD
include_saturdaysNoCount Saturdays as working days. Default false (Monday to Friday only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_saturdays / description
      Added value: +"Count Saturdays as working days. Default false (Monday to Friday only)"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely non-obvious behavior: inclusive boundary counting, SA-specific holiday exclusion, and the Saturday toggle. It does not state the return shape (a numeric count), which is the main missing behavioral detail given there is no output schema.

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?

Two sentences, no filler, and the core behavior (what is counted and what is excluded) is front-loaded ahead of the softer use-case framing. Every clause carries information an agent would otherwise have to infer.

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 simple three-parameter calculation tool with full schema coverage and a read-only annotation, the description covers nearly everything needed to invoke it correctly. The one gap is that the returned value is never characterized, and with no output schema the agent must guess it is a single integer.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by clarifying that the range is inclusive and that include_saturdays is genuinely optional rather than required. The YYYY-MM-DD format is left entirely to the schema, which is acceptable at full coverage.

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?

States a precise verb and resource: counts South African working days between two dates, with the exclusion rule (weekends and public holidays) spelled out. That specificity separates it from a generic date-math tool, though it never names sibling tools like public_holidays, so the differentiation is implicit rather than explicit.

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 gives concrete use contexts (notice periods, payment terms, delivery dates), which tells an agent when this tool is the right fit. It stops short of naming an alternative or stating when-not to use it, so it sits at clear-context without exclusions.

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