Skip to main content
Glama

reference-data

by dev.usaref

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.1/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: paid ($0.02), weekend handling (Egypt's Fri-Sat shown as example), holiday application, return of holiday names and next working day, max range of 366 days, and payment mechanism via api_key or x402.

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?

The description is fairly concise and front-loaded with key facts (cost). However, it is a single long sentence that could be better structured for readability.

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 there is no output schema, the description explains return values (holidays hit and next working day). It covers the main behavior and constraints, though could detail error cases.

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%, so the schema already documents parameters. The description only adds context about api_key usage for payment, adding minimal value beyond schema.

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 statutory holidays, and returns holidays hit and next working day. It is specific and distinguishes 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 Guidelines3/5

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

The description mentions payment but does not provide explicit guidance on when to use this tool versus alternatives. It is implied for counting working days but no exclusions or comparisons.

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.1/5.0
Disambiguation4/5

Most tools have clear, distinct purposes: minimum wage checking, income tax, VAT, working days, holidays, settlement dates, and generic series access all serve different functions. However, compute_vat and check_minimum_wage could be confused with simple get_series lookups for the same series (vat, minimum-wage), though the descriptions clarify that the compute_* tools provide breakdowns rather than just current values.

Naming Consistency4/5

The majority of tools follow a consistent verb_noun snake_case pattern (check_minimum_wage, compute_income_tax, compute_vat, count_working_days, get_public_holidays, get_series, get_series_history, get_snapshot, list_series). Settlement_date breaks the pattern as a noun-only name instead of something like get_settlement_date, creating a minor deviation.

Tool Count5/5

With 10 tools, the server is well-scoped for its reference-data purpose. It covers a broad but justified range of statutory and financial reference data without being excessive, and each tool serves a distinct function within that domain.

Completeness5/5

The tool set provides comprehensive coverage of typical reference data: minimum wage, income tax, VAT, public holidays, working days, settlement dates, and generic series with current values, history, and snapshots. The inclusion of list_series for discovery and the generic get_series/get_series_history endpoints cover the full lifecycle of accessing reference data. No obvious gaps for the stated purpose.

Resources