Skip to main content
Glama

Ezkielyna Public Tools

Tambah hari kerja / Add working days

hari_kerja_berikutnya
Read-onlyIdempotent

Tanggal setelah N hari kerja dari suatu tanggal (untuk SLA, tenggat, estimasi pengiriman). N negatif = mundur. N=0 = hari kerja terdekat. Adds N Indonesian working days to a date (start date not counted), skipping weekends, holidays and optionally cuti bersama.

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": {
      "n": "<n>"
    },
    "name": "hari_kerja_berikutnya"
  }
}

Input Schema

NameRequiredDescriptionDefault
nYesWorking days to add (negative = go back, 0 = this date if it is a working day, else the next one).
dateNoStart date. Date as YYYY-MM-DD (also DD-MM-YYYY, DD/MM/YYYY, or "today"/"hari ini" in Asia/Jakarta). Default today.
cuti_bersama_offNoTreat cuti bersama (collective leave) as a day off. Default true. Set false for businesses that work on cuti bersama.
saturday_workingNoSaturday is a working day (6-day work week). Default false. National holidays on Saturday stay off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond them: weekends, national holidays, and optionally cuti bersama are skipped, and the start date is not counted. It does not describe the return format, but that is minor for a pure date calculation.

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 both languages are given for an Indonesian-context tool, which is reasonable. The Indonesian and English sentences duplicate the same content, adding some length, but nothing is wasted verbosity.

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 four-parameter date-arithmetic tool with full schema coverage and a clean annotation set, the definition gives enough: counting rule, holiday handling, and the Saturday work-week toggle. No output schema exists, yet the return value (a resulting date) is obvious from the purpose statement.

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 coverage is 100%, and each parameter is already well documented, including the negative/zero behavior of n. The description restates the N semantics and adds the 'start date not counted' convention, which is useful but largely redundant with the schema's 'this date if it is a working day' wording. Baseline 3 is appropriate.

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: adding N working days to a start date, with the sign convention and the 'start date not counted' rule. It also names concrete use cases (SLA, deadlines, shipping estimates). It does not explicitly distinguish itself from the sibling hitung_hari_kerja, which likely counts working days between two dates.

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?

Usage context is clear from the stated scenarios (SLA, tenggat, estimasi pengiriman) and the N sign semantics (negative = backward, 0 = nearest working day) tell an agent how to steer the call. There is no explicit 'use this instead of X' statement or exclusion, so it falls short of a 5.

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