Skip to main content
Glama

AutoTasker Hub — China Social Data API

public_holidays

Public holidays by country+year (date.nager.at). ISO-3166. $0.01 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
countryNoCN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful behavioral facts beyond the schema: the upstream data source (date.nager.at) and a per-call price ($0.01 USDC). It does not state that this is a read-only lookup, what the response contains, or what happens for unsupported country codes, leaving meaningful gaps for a definition without annotations.

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?

Three short fragments, front-loaded with the resource and filters, with no filler. The telegraphic style (parenthetical source, bare price token) costs a little readability but wastes no space.

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

Completeness2/5

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

The tool is simple, but with no output schema and no annotations the description should say something about what comes back (holiday names, dates, locales) and about the default year/country being applied silently. For a two-parameter paid lookup, the definition leaves an agent guessing at the response shape.

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 0%, so the schema says only that 'country' is a string defaulting to CN. The description partially compensates by specifying ISO-3166 as the expected code format, which is genuinely useful. It adds nothing about the 'year' parameter (range, whether future years are supported) or about default behavior.

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 names a specific resource and its two filters ('Public holidays by country+year'), which is enough to distinguish it from every listed sibling, none of which return holiday data. It lacks a verb and does not explicitly contrast with any alternative, but the resource is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisite statement, and no mention of alternatives. The only implicit usage hint is the ISO-3166 constraint on the country value.

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.