Skip to main content
Glama

Crypto & Macro Market Data (Tanod)

get_public_holidays

Read-onlyIdempotent

utilpeek: public holidays of a country for a year. To count working days use count_or_add_business_days. An unsupported country, subdivision, language or year is a 422 naming the supported values (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Computed from the python-holidays rules (MIT), not an official calendar: lunar, religious and one-off holidays can be estimates or missing for some years; confirm with an official source for legal or payroll use. Docs: https://tanod.dev/learn/public-holidays-api.html

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>",
      "year": "<year>"
    },
    "name": "get_public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear.
countryYesISO 3166-1 alpha-2 country code (e.g. US, GB, PH).
languageNoHoliday-name language (e.g. en_US).
subdivisionNoSubdivision code or name (e.g. CA).

Output Schema

NameRequiredDescriptionDefault
noteNo
yearNo
countNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sourceNo
countryNo
holidaysNo
languageNo
subdivisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / country / title
      Removed value: -"Country"
    • removedInput schema / properties / language / default
      Removed value: -null
    • changedInput schema / properties / language / description
      Previous value: -"Optional holiday-name language (e.g. en_US)."New value: +"Holiday-name language (e.g. en_US)."
    • removedInput schema / properties / language / title
      Removed value: -"Language"
    • removedInput schema / properties / subdivision / default
      Removed value: -null
    • changedInput schema / properties / subdivision / description
      Previous value: -"Optional subdivision code or name (e.g. CA)."New value: +"Subdivision code or name (e.g. CA)."
    • removedInput schema / properties / subdivision / title
      Removed value: -"Subdivision"
    • changedInput schema / properties / year / description
      Previous value: -"Year (1990-2100)."New value: +"Year."
    • removedInput schema / properties / year / title
      Removed value: -"Year"
    • removedInput schema / title
      Removed value: -"get_public_holidaysArguments"
    • removedOutput schema / properties / holidays / items
      Removed value: -{
      -  "properties": {
      -    "date": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "name": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "weekday": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "country": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "holidays": {
      +      "items": {
      +        "properties": {
      +          "date": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "weekday": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "language": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "properties": {
      +        "library": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "url": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "subdivision": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "year": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely non-schema behavior: a 422 with supported values on bad input and no charge for it, ~0.1s latency, $0.001 price with 10 free calls per IP per UTC day, plus a provenance caveat that lunar/religious/one-off holidays may be estimates or missing. That is substantial behavioral disclosure beyond structured fields.

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?

Front-loads purpose first, then the alternative, then error behavior, cost and caveats. Dense but nearly every clause carries usable information; the pricing/free-tier sentence is the least essential for tool selection and the run-on punctuation makes it slightly harder to scan.

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

Completeness5/5

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

An output schema exists, so return values need no prose. For a read-only lookup the description covers cost, rate limits, error semantics, latency and accuracy caveats, which is everything an agent needs to decide and to hedge its answer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baselines would be 3, but the description adds meaning the schema cannot: an out-of-domain country, subdivision, language or year is a 422 that names the supported values, which tells the agent the enum space is constrained even though the schema shows only regex patterns. It also documents the data source behind those values.

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?

States a specific resource (public holidays), the scoping dimensions (a country, a year), and explicitly contrasts itself with count_or_add_business_days for the working-day use case. An agent can tell exactly what it retrieves without opening the schema.

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?

Names the alternative tool and the condition that selects it ('To count working days use count_or_add_business_days'), which is real routing guidance. It gives no explicit when-not-to-use conditions or prerequisites beyond that single redirect.

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.