Skip to main content
Glama

Ezkielyna Public Tools

Cek tanggal / Check a date

cek_tanggal
Read-onlyIdempotent

Cek apakah suatu tanggal libur nasional, cuti bersama, akhir pekan, atau hari kerja, beserta alasannya. Checks whether a date is a holiday, weekend or working day in Indonesia, with the reason. Default date: today (Asia/Jakarta).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cek_tanggal"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate 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.5/5.0
Behavior3/5

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

Annotations already establish that this is a safe, idempotent, closed-world read. The description adds real domain context beyond them: the scope is Indonesia, the reference timezone is Asia/Jakarta, and the response includes a reason for the classification. It does not describe the actual response shape, which matters since no output schema exists.

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 tight sentences with the purpose front-loaded and the default/timezone constraint second. The Indonesian/English duplication is deliberate for bilingual reach and costs little, though it does repeat the same content twice.

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 single-date classifier with full schema coverage and read-only annotations, the description covers scope, defaults, timezone, and that a reason is returned. The only gap is the exact structure of the returned classification, which is not implied by any output schema.

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%, so all three parameters and the accepted date formats are already documented in the schema. The description's only parameter-adjacent addition is the today/Asia/Jakarta default, which the schema also states, so it adds no meaning beyond the structured data.

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 ('Cek apakah suatu tanggal...') and enumerates the outcomes it distinguishes: national holiday, cuti bersama, weekend, working day, plus a reason. It does not name a sibling (e.g., daftar_libur or hitung_hari_kerja) to sharpen the boundary, so it stops short of a 5.

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 — you call it when you need to classify a single date — and the default ('today, Asia/Jakarta') is stated. There is no explicit when-not guidance and no routing to alternatives such as a bulk holiday list or working-day counting tool.

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