Skip to main content
Glama

indonesia_next_working_day

Read-only

Paid $0.05 per call: the first Indonesian working day after a date, skipping weekends, national holidays and joint-leave days, with each skipped day and its reason.

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

Input Schema

NameRequiredDescriptionDefault
fromNoStart date ISO YYYY-MM-DD; defaults to today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint, it discloses the $0.05 per-call cost, the categories of days skipped, and that the result includes each skipped day with its reason. Holiday-calendar source or coverage limits are not mentioned, but the important invocation and result behavior is well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence front-loads the cost, then states the calculation, skip rules, and returned explanation. Every clause contributes useful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 calculation, the definition supplies cost, geographic scope, skip rules, and result detail while the schema fully covers the optional input. Although there is no output schema, the description adequately summarizes what the response contains.

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 the schema already documents the from parameter's ISO format and default to today. The phrase 'after a date' adds only slight clarification that the result follows the supplied start date.

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 precisely states the operation and scope: finding the first Indonesian working day after a date while skipping weekends, national holidays, and joint-leave days. It does not explicitly differentiate this from indonesia_holiday_check or indonesia_holidays.

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?

Its purpose implies when to use it, namely when an agent needs the next working day rather than just a date. There is no explicit when-not guidance or routing to the holiday lookup siblings for simpler holiday queries.

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