Skip to main content
Glama

Business Day Offset

bpj_business_day_offset
Read-onlyIdempotent

Add or subtract weekdays, excluding listed holidays and the starting day.

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>",
      "offset": "<offset>",
      "holidays": "<holidays>"
    },
    "name": "bpj_business_day_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
offsetYes
holidaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail that the annotations cannot express: that listed holidays AND the starting day are excluded from the weekday count. It still doesn't disclose the return value or how a negative offset that lands on a holiday is resolved.

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?

A single front-loaded sentence with no filler; every clause (add/subtract, weekdays, holidays, starting day) contributes distinct meaning.

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?

For a three-parameter pure function with no output schema, the description should say what is returned and how `holidays` is encoded when empty. Annotations cover the safety side, but the return shape and the holiday-list format remain gaps an agent must guess.

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 0%, so the description carries weight, and it does clarify the counting convention around `start` (the starting day is not counted). But it says nothing about the `holidays` string format or the literal 'none' value, nothing about offset sign/limits, and nothing about the YYYY-MM-DD requirement, leaving the schema titles to do most of that 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: shifting a date by weekdays while skipping holidays. That is precise enough to separate it from date/time siblings such as bpj_convert_timestamp, though no sibling is named explicitly for contrast.

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 only implied: the arithmetic nature of the tool makes its purpose obvious, but the description never says when to prefer it over a plain date conversion or timestamp tool, and it gives no prerequisites or 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.