Skip to main content
Glama

Tinplate Edge AI Safety, Security & EU Compliance

tinplate_workday_holiday_is_workday

Read-onlyIdempotent

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

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": {
      "date": "<date>",
      "country": "<country>"
    },
    "name": "tinplate_workday_holiday_is_workday"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesTarget calendar date to inspect in YYYY-MM-DD format.
countryYesISO 3166-1 alpha-2 country code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / date / description
      Added value: +"Target calendar date to inspect in YYYY-MM-DD format."
  2. Changed7 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 / date / description
      Removed value: -"Parameter 'date' (e.g. \"2026-11-16\")"
    • addedInput schema / properties / date / example
      Added value: +"2026-04-03"
    • addedInput schema / properties / date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedInput schema / required
      Previous value: -[
      -  "country",
      -  "date"
      -]New value: +[
      +  "date",
      +  "country"
      +]
  3. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful domain detail (13 supported countries, HU swap Saturdays), but it never states the shape of the result (a boolean workday verdict), which is the key behavioral fact for a predicate endpoint.

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?

Short and front-loaded, but the parenthetical endpoint path (POST /v1/workday-holiday/is-workday) consumes space without helping tool selection, and the SLA/business-day phrasing is boilerplate that does not match the single-date predicate.

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?

With two required, fully documented parameters and annotations covering safety, the definition is callable. However, there is no output schema, so the description should say what comes back (boolean vs object, holiday name, etc.), and it does not.

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 coverage is 100%, so date format, the ISO country pattern and the 13-value enum are all documented in the schema. The description's mention of country count and HU swap Saturdays adds marginal domain color but no parameter syntax or constraint beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and domain ("Calculate business days and SLA deadlines across 13 countries") and gives the endpoint path, but it reads like a group-level blurb rather than a statement of this specific operation. Nothing tells the agent this endpoint answers a yes/no question for one date, nor how it differs from siblings tinplate_workday_holiday or tinplate_workday_holiday_add.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. The agent is not told when to pick this single-date check versus the related workday tools, and no prerequisite or exclusion is stated.

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