Skip to main content
Glama

indonesia_holiday_check

Read-only

Paid $0.05 per call: is one date an Indonesian public holiday or joint-leave day, plus weekend status and the next holiday. Answers "can we operate that day" directly.

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": {
      "date": "<date>"
    },
    "name": "indonesia_holiday_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate to test, ISO YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses the per-call cost ($0.05) and enumerates what comes back: holiday/joint-leave verdict, weekend status, and the next holiday. That is real added context for an agent deciding whether to spend a call. It stops short of covering edge behavior such as invalid dates or timezone assumptions.

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 no filler. The cost disclaimer is placed ahead of the purpose, which slightly delays the front-loading of what the tool does, but the whole description is short enough that nothing is wasted.

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 one-parameter, read-only lookup with no output schema, the description covers the verdict, the auxiliary fields (weekend, next holiday), and the cost, which is what an agent needs to call it correctly. Only minor gaps remain around input validation and date/timezone handling.

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% and the single `date` parameter already documents the ISO YYYY-MM-DD format. The description adds no further semantics about the parameter, so the baseline of 3 applies.

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?

States a specific verb and resource: tests one date against Indonesian public holidays and joint-leave days, and also returns weekend status plus the next holiday. That is clearly narrower than the list-oriented sibling indonesia_holidays, but the description never names siblings like indonesia_next_working_day, so differentiation is inferred 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?

The phrase "Answers 'can we operate that day' directly" implies the use case (single-date operational check), but there is no explicit when-not guidance and no mention of when to prefer indonesia_holidays or indonesia_next_working_day. Usage is implied rather than prescribed.

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