Skip to main content
Glama

reference-data

by dev.latamref

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.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description discloses payment, range limits, and special weekend handling for Egypt. It does not cover error behavior or rate limits, but provides essential behavioral context.

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?

Three concise sentences front-load the paid nature, clearly state functionality, limits, and API key guidance. No unnecessary words; every sentence adds value.

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?

Covers main functionality, inputs, and a key constraint (max 366 days). Lacks explicit output schema but mentions returned elements (holidays, next working day). Sufficient for the tool's complexity.

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%, baseline 3. The description adds context about weekends per country, max range implying from/to constraints, and optional api_key usage, enhancing the schema descriptions.

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 it counts working days in a date range for a country, handling weekends and holidays, and distinctively mentions returning holiday names and the next working day, differentiating it from siblings like get_public_holidays.

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 indicates the tool is paid, notes a max range of 366 days, and advises on API key usage or payment instructions. However, it does not explicitly contrast with siblings or provide when-not-to-use guidance.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation: compliance check, tax computation, VAT breakdown, day counting, holiday retrieval, series value/history/snapshot, catalog listing, and settlement date calculation. Even where underlying data overlaps (e.g., minimum wage as a series), the outputs and use cases are clearly differentiated.

Naming Consistency4/5

Nine of ten tools follow a clear verb_noun pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). The outlier is settlement_date, which uses a noun phrase rather than a verb-based name, though it remains unambiguous and readable.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose, covering tax, wages, holidays, working days, series discovery, and settlement dates. Each tool earns its place without redundancy or bloat.

Completeness5/5

The surface provides comprehensive coverage: discovery via list_series, current/historical data via get_series and get_series_history, a full snapshot, tax computations, wage compliance, public holidays, working day counts, and settlement date calculations. There are no obvious gaps or dead ends for the intended domain.

Resources