Skip to main content
Glama

Ezkielyna Public Tools

Daftar hari libur / List holidays

daftar_libur
Read-onlyIdempotent

Daftar libur nasional dan cuti bersama Indonesia per tahun (opsional per bulan), sesuai SKB 3 Menteri, lengkap dengan nomor SKB dan sumber. Lists Indonesian national public holidays and collective leave for 2025, 2026, 2027. Offline, free.

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": {
      "year": "<year>"
    },
    "name": "daftar_libur"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear (2025, 2026, 2027).
monthNoOptional month 1-12.
include_cuti_bersamaNoInclude cuti bersama (collective leave). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond the annotations: data provenance (SKB 3 Menteri, with decree numbers and sources) and the covered year range 2025-2027, plus 'offline, free'. It still says nothing about response shape or whether the list is ordered, which is a modest 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?

Two front-loaded sentences with the coverage and provenance stated early; the bilingual phrasing and 'offline, free' tag are short and relevant. There is mild redundancy with the title and a little promotional filler, but nothing wasteful.

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 simple three-parameter lookup with no output schema and full annotation coverage, the definition supplies what an agent needs: scope, year bounds, data source, and the fact that results include decree numbers. Only the return structure is left implicit, which is acceptable here.

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 three parameters, including year, month, and include_cuti_bersama, are already documented in the schema. The description reinforces the optionality of the month and the presence of cuti bersama in the results, but it adds no semantics or edge cases, so it sits at the baseline.

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: listing Indonesian national holidays and collective leave, per year (optionally per month), citing SKB 3 Menteri. It is clearly not a working-day calculator, but it never names or contrasts with the closest siblings, such as hitung_hari_kerja or hari_kerja_berikutnya, so differentiation is implied rather than stated.

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?

It implies when to use the tool: look up holidays for a given year, optionally narrowed to a month. It gives no explicit when-not guidance, no prerequisites, and no pointer to an alternative such as a working-day counter, so the usage context is only implied.

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