Skip to main content
Glama

Federal legal holidays for a year

federal_legal_holidays
Read-only

List the legal holidays for a year under FRCP 6(a)(6) and FRAP 26(a)(6): the eleven days in 5 U.S.C. 6103(a), the Friday observed for a Saturday holiday (5 U.S.C. 6103(b)(1)), the Monday observed for a Sunday holiday (Executive Order 11582), and the days the President closed the executive branch. These are the days a federal deadline rolls off. Each observed or closure day says which reading treats it as a legal holiday and that the point is not settled. State holidays are not applied.

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

Input Schema

NameRequiredDescriptionDefault
yearYesFour-digit year, 2024 to 2030.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only and closed-world, so the description carries the real burden and does: it discloses the inclusion rule set (eleven statutory days, Friday/Monday observance, presidential closures) and warns that each ambiguous day is flagged as unsettled rather than silently resolved. It also states the state-holiday exclusion, which materially affects results.

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 sentences, front-loaded with the scope and ending with the exclusion — every clause carries scope information. The stacked statutory parentheticals are dense but each one defines a distinct category of holiday, so they earn their place.

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?

For a single-parameter, read-only reference tool with no output schema, the description covers inclusion rules, ambiguity handling, and exclusions, which is everything an agent needs to trust and use the result. Nothing material is left to inference.

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% and the single `year` parameter already documents its 2024-2030 range, so the schema does the work. The description adds nothing about the year argument beyond implying a single year is evaluated; baseline 3 applies.

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 verb and resource ("List the legal holidays for a year") and pins the scope to named authorities (FRCP 6(a)(6), FRAP 26(a)(6), 5 U.S.C. 6103). The enumeration of what counts as a holiday makes it clearly distinct from the sibling tools that count days or compute deadlines.

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?

The sentence "These are the days a federal deadline rolls off" gives a concrete use context, and "State holidays are not applied" is an explicit exclusion. It does not, however, name a sibling or say when to prefer federal_count_days or federal_deadline over this reference list.

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