Skip to main content
Glama
Sign In

X3 Compliance

by io.github.x3allamerican
OverviewDiscussionsAdmin

U.S. federal holidays

us_federal_holidays
Read-onlyIdempotent

The 11 U.S. federal holidays for a year, as observed (weekend holidays moved to Friday or Monday).

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

Input Schema

NameRequiredDescriptionDefault
yearYesYear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 safety is covered. The description adds real behavioral context the annotations do not: the fixed count of 11 and the weekend-shift observation rule, which is the detail an agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the resource and scope, with the observation rule as a parenthetical. Nothing is wasted and nothing important is buried.

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 trivial one-parameter lookup with no output schema, the description conveys enough: what is returned, how many entries, and how observed dates are computed. It does not say whether the response is date strings, names, or pairs, which is the only notable remaining gap.

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% with a single required `year` parameter, so the schema already carries the parameter meaning. The description only implies that the year selects which holiday set is returned and adds no format or range guidance beyond that.

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?

States a specific resource (U.S. federal holidays), a precise scope (11 per year), and the observation rule (weekend holidays moved to Friday or Monday). It does not explicitly distinguish itself from any sibling, but none of the listed siblings overlap in domain.

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?

No explicit when-to-use, when-not, or alternative is given. Usage is only implied by the narrow scope of the tool, which is adequate for a single-parameter lookup but leaves an agent to infer that this is the canonical source for holiday dates rather than, say, cfr_changes.

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

All X3 Compliance 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