Skip to main content
Glama

update-public-holiday

Update an existing public holiday by providing its ID and modifying fields such as name, date, region, type, or active status.

Instructions

Update an existing public holiday

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
holiday_idYesThe public holiday ID
nameNoHoliday name
dateNoHoliday date (YYYY-MM-DD)
regionNoRegion or country code
countryNoCountry name
typeNoHoliday type (bank_holiday, observed, etc.)
moveableNoMoveable status (0=fixed, 1=moveable)
recurringNoRecurring status (0=one-time, 1=recurring)
yearNoYear for the holiday
notesNoAdditional notes
activeNoActive status (1=active, 0=archived)
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only indicates mutation ('Update') but omits any side effects, permissions, or update semantics (e.g., partial updates).

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?

The description is a single, efficient sentence that is front-loaded and contains no unnecessary information.

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?

Given the complexity (11 parameters, no output schema, no annotations), the description lacks context on return values, error handling, and field update behavior, making it incomplete.

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 descriptions for all parameters. The description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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?

The description 'Update an existing public holiday' clearly states the action (update) and the resource (public holiday), distinguishing it from siblings like create-public-holiday or delete-public-holiday.

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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description is minimal.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asachs01/float-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server