Skip to main content
Glama

Ezkielyna Public Tools

Hitung hari kerja / Count working days

hitung_hari_kerja
Read-onlyIdempotent

Menghitung jumlah hari kerja di antara dua tanggal (tidak termasuk akhir pekan, libur nasional, dan opsional cuti bersama). Counts Indonesian working days between two dates, inclusive of both by default. Reversed ranges are swapped.

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": "hitung_hari_kerja"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd date (inclusive). Date as YYYY-MM-DD (also DD-MM-YYYY, DD/MM/YYYY, or "today"/"hari ini" in Asia/Jakarta).
startYesStart date. Date as YYYY-MM-DD (also DD-MM-YYYY, DD/MM/YYYY, or "today"/"hari ini" in Asia/Jakarta).
count_startNoCount the start date itself. Default true. Set false for "working days after start, up to and including end".
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context: the range is inclusive of both endpoints by default, weekends and national holidays are always excluded, cuti bersama is optionally excluded, and reversed ranges are auto-swapped rather than erroring.

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?

Two short sentences, front-loaded with the purpose. The Indonesian and English sentences partially duplicate each other, but the English version carries non-redundant facts (inclusivity default, range swapping), so the repetition is mostly justified for a bilingual tool.

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 five-parameter, non-destructive calculation tool with no output schema, the description plus the fully documented schema give the agent everything needed to invoke it. The only gap is that it never states the return value is a day count (a number), which the agent must infer from the tool name.

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 all five parameters (including count_start, cuti_bersama_off, saturday_working) are already documented in the schema with defaults and formats. The description only restates that cuti bersama is optional and that both endpoints are counted by default, adding no syntax or edge-case detail beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Menghitung jumlah hari kerja di antara dua tanggal' / 'Counts Indonesian working days between two dates') and immediately qualifies the scope with the exclusions (akhir pekan, libur nasional, cuti bersama). This clearly separates it from a next-working-day style sibling such as hari_kerja_berikutnya.

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 date-range framing and the 'opsional cuti bersama' wording, and 'Reversed ranges are swapped' tells the agent it need not pre-order inputs. However, there is no explicit when-to-use/when-not guidance and no named alternative for the adjacent question of finding the next working day.

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