Skip to main content
Glama

Australia Business Calendar MCP

business_days

PRO. Add/subtract N Australian business days from a date (national holiday set).

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>",
      "days": "<days>"
    },
    "name": "business_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYes
startYes
access_tokenNoSubscriber token from /success (or Authorization: Bearer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It usefully discloses that calculations use the Australian national holiday set and that both addition and subtraction are supported, but it omits the expected date format, timezone assumptions, how negative or zero offsets behave, and what the return value looks like.

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?

The description is two short sentences, front-loaded with the core operation and scope, with no redundant or filler content.

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 simple calculation tool with no output schema, the description covers the core operation and holiday basis. However, it leaves out the date format expected for 'start', the format of the returned date, and any behavior around non-business starting dates, which an agent would need to invoke it reliably.

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 only 33%, with only the access_token parameter documented in the schema. The description partially compensates by clarifying that 'days' is a signed offset (add/subtract N) and that 'start' is a base date, but it does not specify date syntax or constraints such as whether zero is allowed.

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 operation (add/subtract N business days) and a precise resource (Australian business days using the national holiday set). The purpose is clear without opening the schema, though it does not explicitly differentiate itself from siblings like due_date or next_holidays.

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

Usage Guidelines2/5

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

Aside from the 'PRO' tag implying a paid/subscriber feature, there is no guidance on when to use this tool versus due_date or next_holidays. No exclusions, prerequisites, or alternative-routing instructions are provided.

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.