reference-data

count_working_days

Read-onlyIdempotent

PAID ($0.002). 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 (instant card checkout at /pricing); otherwise the response explains how to pay via x402. The evaluation country is free to try (see list_series). Optional receipt (boolean, default false): on a paid success, include an Ed25519 answer receipt at no extra USDC. An answer receipt is not a series certified extract (GET /v1/certified/{country}/{series} is $0.10 and is not an MCP tool) and is not legal advice. Verify with verify_answer_receipt against /certified/public-key.

Input Schema

Name	Required	Description
`to`	Yes	Range end, YYYY-MM-DD, inclusive
`from`	Yes	Range start, YYYY-MM-DD, inclusive
`api_key`	No	API key
`country`	Yes	ISO country code
`receipt`	No	Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool).
`subdivision`	No	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.

Output Schema

Name	Required	Description
`basis`	No
`error`	No	Present on a free refusal or error; no charge
`status`	No	Answer status, e.g. computed or an honest no-answer status
`country`	No
`receipt`	No	Ed25519 answer receipt when receipt=true on a paid success
`question`	No
`no_charge`	No
`price_usd`	No
`disclaimer`	No
`how_to_pay`	No
`provenance`	No	Cited official sources behind the answer
`bind_series`	No
`explanation`	No
`label_basis`	No	Inputs and the rule ids that produced the two labels
`x_next_bind`	No
`http_endpoint`	No
`coverage_label`	No	How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules
`confidence_label`	No	Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules
`payment_required`	No	true when the call needs payment; how_to_pay explains x402 or card

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 17, 2026

changedInput schema / properties / receipt / description

Previous value: -"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool)."New value: +"Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.10; that SKU is not an MCP tool)."

removedOutput schema / properties / label_basis / properties / source_type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / label_basis / properties / source_type / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / label_basis / properties / verification_age_days / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / label_basis / properties / verification_age_days / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed3 schema fields changedOct 13, 2026

addedOutput schema / properties / confidence_label

Added value: +{
+  "description": "Evidence verdict derived from source type, verification age and the stale flag (answers: the weakest series read). Rules at /label-rules",
+  "enum": [
+    "high",
+    "medium",
+    "low"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / coverage_label

Added value: +{
+  "description": "How much of the question is covered: ready = complete; partial = held with a disclosed limitation or default; gap = no number served. Rules at /label-rules",
+  "enum": [
+    "ready",
+    "partial",
+    "gap"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / label_basis

Added value: +{
+  "additionalProperties": {},
+  "description": "Inputs and the rule ids that produced the two labels",
+  "properties": {
+    "confidence_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage_reasons": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "inputs": {
+      "items": {},
+      "type": "array"
+    },
+    "rules": {
+      "type": "string"
+    },
+    "rules_version": {
+      "type": "string"
+    },
+    "source_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "stale": {
+      "type": "boolean"
+    },
+    "verification_age_days": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "Working-day count over a range with holidays hit",
+  "properties": {
+    "basis": {},
+    "bind_series": {},
+    "country": {
+      "type": "string"
+    },
+    "disclaimer": {},
+    "error": {
+      "description": "Present on a free refusal or error; no charge"
+    },
+    "explanation": {},
+    "how_to_pay": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "http_endpoint": {
+      "type": "string"
+    },
+    "no_charge": {
+      "type": "boolean"
+    },
+    "payment_required": {
+      "description": "true when the call needs payment; how_to_pay explains x402 or card",
+      "type": "boolean"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provenance": {
+      "description": "Cited official sources behind the answer"
+    },
+    "question": {},
+    "receipt": {
+      "description": "Ed25519 answer receipt when receipt=true on a paid success"
+    },
+    "status": {
+      "description": "Answer status, e.g. computed or an honest no-answer status",
+      "type": "string"
+    },
+    "x_next_bind": {}
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / receipt

Added value: +{
+  "default": false,
+  "description": "Default false. When true, a paid success includes an Ed25519 answer receipt (kind answer_receipt) at no extra USDC. Unpaid 402 and free refusals do not include one. Not a series certified extract (GET /v1/certified/{country}/{series} at $0.25; that SKU is not an MCP tool).",
+  "type": "boolean"
+}

Changed1 schema field changedJul 28, 2026

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"
+}

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bb",
-  "bo",
-  "br",
-  "bz",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "jm",
-  "mx",
-  "ni",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "tt",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "gy",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 24, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "bo",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "hn",
-  "mx",
-  "pa",
-  "pe",
-  "py",
-  "sv",
-  "uy"
-]New value: +[
+  "ar",
+  "bb",
+  "bo",
+  "br",
+  "bz",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "jm",
+  "mx",
+  "ni",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "tt",
+  "uy"
+]

Changed1 schema field changedJul 20, 2026

changedInput schema / properties / country / enum

Previous value: -[
-  "ar",
-  "br",
-  "cl",
-  "co",
-  "cr",
-  "do",
-  "ec",
-  "gt",
-  "mx",
-  "pe",
-  "py",
-  "uy"
-]New value: +[
+  "ar",
+  "bo",
+  "br",
+  "cl",
+  "co",
+  "cr",
+  "do",
+  "ec",
+  "gt",
+  "hn",
+  "mx",
+  "pa",
+  "pe",
+  "py",
+  "sv",
+  "uy"
+]

AddedJul 17, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on substantially more: a stated price ($0.002), auth/payment mechanics (api_key vs x402 402 responses), the refusal behavior for unknown subdivisions and free tier, and the receipt option including what it is not. This is exactly the kind of context annotations cannot carry.

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

Conciseness3/5

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

Purpose and price are correctly front-loaded, but the single paragraph crams in payment mechanics, receipt/legal disclaimers, an unrelated $0.10 certified-extract SKU, and a verification pointer, with the receipt explanation largely restating the schema field. Several sentences do not earn their place in a tool-selection description.

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?

Given an output schema exists, the description need not explain returns; it instead covers the open-world concerns an agent actually needs — cost, auth path, free tier, 366-day cap, receipt semantics, and how to verify. Nothing required to call this correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description still adds value by explaining that api_key enables instant paid access, that the evaluation country is free, and by cross-referencing where subdivision codes originate (get_public_holidays). Some receipt text is duplicated verbatim from the schema, which limits the net gain.

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 opening clause names a specific verb+resource ('Working days in a date range for a country') and enumerates the exact computation (weekends with Egypt's Fri–Sat, statutory holidays) plus the ancillary outputs (holidays hit by name, next working day after the range). This is clearly distinguishable in substance from sibling add_business_days, though it never explicitly names the closest sibling business_days_between as the alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operating guidance: pass api_key if available, the evaluation country is free to try, range is capped at 366 days, and unpaid calls return an x402 payment explanation rather than an error. It does not, however, state when to prefer this over overlapping siblings like business_days_between, so it stops short of a full when/when-not routing rule.

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

All reference-data tools Inspect

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

Need Help?