Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Working Days

WorkingDays
Read-only

Working Days: Working Days is a working days and business days API that counts the working days and non-working days for any country and month. Pass a two-letter country code and month number to get total counts, working date lists, and non-working days marked with holiday names. On paid plans, add a state or region for regional holidays, set a custom weekend, count between any two dates, or add business days to a date. (Cost: 2 credits)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "WorkingDays"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date (YYYY-MM-DD), inclusive. Used with start
yearNoThe year you want to get the number of working days for
monthNoThe month you want to get the number of working days for
startNoStart date (YYYY-MM-DD). With end, counts working days across that range (up to 366 days, inclusive) instead of a month. With addDays, the date to count from (defaults to today)
regionNoOptional state or region code within the country for regional public holidays (e.g. CA for California, BY for Bavaria)
addDaysNoNumber of working days to add to start (negative to subtract). The start date itself is not counted. Returns resultDate plus the days it stepped over
countryYesThe 2-letter country code you want to get the number of working days for
weekendNoComma-separated weekend days as names or numbers 0-6 (Sunday=0), or none. Defaults to sat,sun

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, open-world, non-destructive behavior. The description adds valuable context beyond them: certain capabilities require a paid plan, each call costs 2 credits, and it summarizes returned counts, date lists, and holiday names. It does not cover error behavior or rate limits, so 4 rather than 5.

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 reasonably short and front-loads the core purpose and basic input pattern. It includes redundant name restatement ('Working Days: Working Days is...') and a long paid-plan feature sentence, but there are no major structural problems.

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?

For an 8-parameter tool with a full schema and an output schema, the description supplies the important missing context: paid-plan gating, credit cost, and the kinds of results returned. It is slightly incomplete because it says to pass a month even though only country is required and does not mention month/year defaults, but the schema covers those details.

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 parameter meanings are already well documented. The description still adds useful mode-level meaning by grouping region, weekend, start/end, and addDays as paid-plan options, which helps an agent understand parameter combinations. It does not add syntax detail beyond the schema.

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 states a specific verb and resource: counting working and non-working days for a country and month, with optional regional, custom-weekend, date-range, and addDays modes. It is clear what the tool does, but it never names or contrasts with relevant siblings such as WorldHolidays, DateCalculator, or DueDateCalculator, so it falls short of full sibling differentiation.

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?

It describes the basic invocation pattern (country plus month) and explains that region, custom weekend, date ranges, and addDays are paid-plan features. However, it gives no explicit when-to-use/when-not guidance or alternative tool routing, leaving usage largely implied.

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

All APIVerve 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