Skip to main content
Glama

curatedapi

Excel NETWORKDAYS function: working days between dates

calc_excel_networkdays
Read-only

Working days between two dates, both included, with holidays and any weekend, as Excel's NETWORKDAYS and NETWORKDAYS.INTL.

NETWORKDAYS.INTL(start_date, end_date, [weekend], [holidays]); with the default weekend it is NETWORKDAYS. Both dates count. Negative when end is before start.

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_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "calc_excel_networkdays"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoPrecision and rounding of the results (default: rounding=half_even, decimals=0).
weekendNoWeekend days, as in NETWORKDAYS.INTL: a weekend number ("1" Saturday and Sunday, "2" Sunday and Monday, ... "7" Friday and Saturday, "11" Sunday only, ... "17" Saturday only) or seven 0s and 1s starting on Monday, 1 for a weekend day ("0000011" is Saturday and Sunday). At most 7 characters.1
end_dateYesEnd date.
holidaysNoDates that are not working days. Up to 1000 items.
start_dateYesStart date.

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world behavior, yet the description still adds real behavioral facts: inclusivity of both endpoints, that a negative value is returned when end precedes start, and that the default weekend applies. It does not explain the interaction of the nested options rounding with day counting, leaving a small gap.

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 in the first clause and the whole text is three short sentences. The middle sentence restates the signature that the input schema already encodes, which is mild redundancy but not harmful.

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 read-only date-arithmetic tool with a full output schema, the description covers semantics, inclusivity, negative results, and weekend customization, which is enough to call it correctly. The only shortfall is the lack of sibling differentiation among several date-related tools.

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 each parameter is already documented in the schema; the description adds only the default-weekend clarification and the INTL correspondence. No extra syntax, format, or edge-case meaning is supplied for weekend codes, holidays, or the nested options object, so the baseline of 3 applies.

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 gives a specific verb and resource (count working days between two dates) with precise scope: both dates inclusive, holidays and arbitrary weekends excluded, matching Excel's NETWORKDAYS/NETWORKDAYS.INTL. It does not distinguish itself from the closely related sibling calc_date_working_days, so an agent must guess which to pick between the two.

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?

Usage is implied by the Excel-function framing and the stated signature, which suggests when this tool applies, but there is no explicit when-to-use/when-not guidance and no alternative named. The agent gets no rule for choosing between this and cal/calc_date_working_days or calc_excel_workday.

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