Skip to main content
Glama

next-federal-holiday

US federal holiday calendar. No input: the next upcoming holiday with days until, and the 2026, 2027, and 2028 eleven-holiday schedules with the Saturday and Sunday observed-date moves flagged, answered fresh on every call. Price: $0.005 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "next-federal-holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses freshness (computed per call), the exact price ($0.005/call in USDC on Base mainnet via x402), and the failure mode (HTTP 402 with machine-readable payment terms). The only gap is that it doesn't describe the response shape in detail, though the content is summarized.

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?

Three sentences, front-loaded with the resource and return content, then the no-input constraint, then payment terms. No filler; each sentence adds distinct information.

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?

No output schema exists, so the description must convey return values, which it does (next holiday with days-until, three years of schedules, observed-date flags). Payment and error behavior are covered; only the precise response format is left implicit, which is a minor gap for a zero-param tool.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; the description reinforces this by stating 'No input', removing any doubt about whether arguments are needed.

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 (US federal holiday calendar) and precisely what is returned: the next upcoming holiday with days-until plus the 2026/2027/2028 eleven-holiday schedules with observed-date moves flagged. This clearly separates it from calendar-adjacent siblings like dst-state, iso-week, and fomc-calendar.

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?

Explicitly says 'No input', telling the agent it can call with an empty object, and 'answered fresh on every call' signals no caching. It lacks explicit when-not or alternative-tool guidance, but the scope is narrow enough that the intended use is unambiguous.

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