Skip to main content
Glama

reference-data

by dev.asiaref
OverviewDiscussionsAdmin

count_working_days

PAID ($0.02). Working days in a date range for a country: weekends (Egypt's Fri–Sat handled) and statutory public holidays applied, with the holidays hit by name and the next working day after the range. Range max 366 days. Pass api_key if you have one; otherwise the response explains how to pay via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRange end, YYYY-MM-DD, inclusive
fromYesRange start, YYYY-MM-DD, inclusive
api_keyNoAPI key
countryYesISO country code
subdivisionNoOptional ISO 3166-2 region code (e.g. 'DE-BY') to apply that region's statutory holidays on top of the national calendar. Regions are listed under `subdivisions` by get_public_holidays. Unknown code is refused free with the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / subdivision
      Added value: +{
+  "description": "Optional ISO 3166-2 region code (e.g. 'DE-BY') to apply that region's statutory holidays on top of the national calendar. Regions are listed under `subdivisions` by get_public_holidays. Unknown code is refused free with the list.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "kz",
-  "lk",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "iq",
+  "jo",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "np",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "uz",
+  "vn"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "bh",
-  "cn",
-  "hk",
-  "id",
-  "il",
-  "in",
-  "jp",
-  "kr",
-  "kw",
-  "my",
-  "om",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "kz",
+  "lk",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "ae",
-  "bd",
-  "cn",
-  "hk",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "pk",
-  "qa",
-  "sa",
-  "sg",
-  "th",
-  "tr",
-  "tw",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "bh",
+  "cn",
+  "hk",
+  "id",
+  "il",
+  "in",
+  "jp",
+  "kr",
+  "kw",
+  "my",
+  "om",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "bd",
-  "id",
-  "in",
-  "jp",
-  "kr",
-  "my",
-  "ph",
-  "sg",
-  "th",
-  "vn"
-]New value: +[
+  "ae",
+  "bd",
+  "cn",
+  "hk",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "pk",
+  "qa",
+  "sa",
+  "sg",
+  "th",
+  "tr",
+  "tw",
+  "vn"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / country / enum
      Previous value: -[
-  "in",
-  "jp",
-  "kr",
-  "ph",
-  "sg"
-]New value: +[
+  "bd",
+  "id",
+  "in",
+  "jp",
+  "kr",
+  "my",
+  "ph",
+  "sg",
+  "th",
+  "vn"
+]
  7. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: handles weekends (including Egypt's Fri-Sat), applies statutory holidays, returns holidays hit by name and next working day, and imposes a max range of 366 days.

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?

The description is concise (two sentences) with key information front-loaded (paid, core function) and no unnecessary words.

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?

While it covers key aspects, the output structure is slightly ambiguous (whether the main return is a count or a list) and lacks explicit error handling, but overall adequate for a parameterized tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds important constraints (max 366 days range, special weekend handling) that are not in the schema, enhancing parameter understanding.

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?

The description clearly states the tool counts working days in a date range for a country, applying weekends and public holidays. It distinguishes from sibling tool 'get_public_holidays' by focusing on counting and returning the next working day.

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 description mentions the tool is paid ($0.02) and provides guidance on payment via api_key or x402, but does not explicitly compare to siblings or state when to use this vs. alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All reference-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources