Skip to main content
Glama
Sign In

tokenguard-mcp

by io.github.eltociear
OverviewDiscussionsAdmin

public_holidays

Public holidays for a country and year, with local names and a past/upcoming flag. (Free. This server also sells a paid API — call paid_catalogue for the routes and prices; x402 over USDC on Base, no signup.)

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": "public_holidays"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCalendar year (defaults to current)
countryYesISO 2-letter country code, e.g. JP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It adds useful behavioral context by stating the response includes local names and a past/upcoming flag, and the parenthetical clarifies that the tool is free and requires no signup. However, it does not disclose error behavior, rate limits, or explicitly confirm read-only status.

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 concise, with the core purpose front-loaded in the first sentence. The second sentence about the paid API is somewhat tangential but still brief and potentially useful for choosing between free and paid options. No wasted words.

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 a simple 2-parameter read-only lookup tool without an output schema, the description adequately conveys the return content (local names, past/upcoming flag) and the cost/auth context. It is missing some details about error cases or data source limitations, but these are not critical for basic usage.

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?

The input schema fully covers both parameters (country and year) with descriptions, so schema coverage is high. The description adds no additional parameter-level semantics beyond what the schema already provides, warranting the baseline score.

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 clearly identifies the resource (public holidays) and its scope (country and year), and distinguishes this tool from sibling data lookup tools. However, it lacks an explicit verb like 'get' or 'returns', so the action is implied 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?

The description implies the tool is used to fetch public holidays for a country and year. It also points to paid_catalogue as an alternative for paid API access, but it does not explicitly state when to use this tool over sibling tools or when not to use it.

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

All tokenguard-mcp 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