Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_workday_holiday

Read-onlyIdempotent

Workday & Holiday Calculator API: Calculate business days and SLA deadlines across 13 countries including HU swap Saturdays. (Endpoint: POST /v1/workday-holiday/between)

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "country": "<country>"
    },
    "name": "tinplate_workday_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesISO 3166-1 alpha-2 country code.
end_dateYesRange end date in YYYY-MM-DD format (on or after start_date; max 3,660 days span).
start_dateYesRange start date in YYYY-MM-DD format.
include_endNoWhether to include end_date in the evaluated range (default true).
include_startNoWhether to include start_date in the evaluated range (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / end_date / description
      Added value: +"Range end date in YYYY-MM-DD format (on or after start_date; max 3,660 days span)."
    • addedInput schema / properties / include_end / description
      Added value: +"Whether to include end_date in the evaluated range (default true)."
    • addedInput schema / properties / include_start / description
      Added value: +"Whether to include start_date in the evaluated range (default true)."
    • addedInput schema / properties / start_date / description
      Added value: +"Range start date in YYYY-MM-DD format."
  2. Changed12 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Parameter 'country' (e.g. \"HU\")"New value: +"ISO 3166-1 alpha-2 country code."
    • addedInput schema / properties / country / enum
      Added value: +[
      +  "HU",
      +  "DE",
      +  "GB",
      +  "US",
      +  "FR",
      +  "ES",
      +  "IT",
      +  "NL",
      +  "AT",
      +  "PL",
      +  "RO",
      +  "SK",
      +  "CZ"
      +]
    • addedInput schema / properties / country / example
      Added value: +"HU"
    • removedInput schema / properties / end_date / description
      Removed value: -"Parameter 'end_date' (e.g. \"2026-08-24\")"
    • addedInput schema / properties / end_date / example
      Added value: +"2026-04-30"
    • addedInput schema / properties / end_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / include_end
      Added value: +{
      +  "example": true,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_start
      Added value: +{
      +  "example": true,
      +  "type": "boolean"
      +}
    • removedInput schema / properties / start_date / description
      Removed value: -"Parameter 'start_date' (e.g. \"2026-08-17\")"
    • addedInput schema / properties / start_date / example
      Added value: +"2026-04-01"
    • addedInput schema / properties / start_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedInput schema / required
      Previous value: -[
      -  "country",
      -  "start_date"
      -]New value: +[
      +  "start_date",
      +  "end_date",
      +  "country"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely useful behavioral nuance ("including HU swap Saturdays") and the country scope, but it never says what the response contains — a count, a list of dates, or an SLA deadline date — and "SLA deadlines" is mentioned despite no SLA parameter existing in the schema, which is mildly misleading.

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?

Two short sentences, front-loaded with the purpose. The trailing HTTP endpoint annotation ("POST /v1/workday-holiday/between") is low-value metadata for an agent selecting a tool, but it is brief and does not obscure the main statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return value, and it does not — an agent cannot tell whether it gets a business-day count, a holiday list, or a computed deadline. Combined with the unexplained "SLA deadlines" claim that has no corresponding parameter, the definition is adequate but leaves a real gap for a calculation tool.

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%, including the country enum and the 3,660-day span limit, so the schema does the heavy lifting and baseline 3 applies. The description adds only country-scope and the HU swap-Saturday behavior; it says nothing about include_start/include_end semantics that the schema does not already state.

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 gives a specific verb+resource ("Calculate business days and SLA deadlines") plus scope ("across 13 countries", endpoint /between). It implicitly separates this range calculation from the sibling _add and _is_workday tools via the "between" framing, but never names them, so differentiation is inferential rather than stated.

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?

Usage is only implied: a start/end range plus country implies "use this for range counts". There is no explicit when-to-use, no when-not-to-use, and no routing to tinplate_workday_holiday_add or tinplate_workday_holiday_is_workday, which are the obvious alternatives for single-day or add-day questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources