Skip to main content
Glama

Update holiday profile

update_holiday_profile
DestructiveIdempotent

Update an existing holiday profile in your organization (name, holiday list, default-for-countries, active flag, or notes). The organization is fixed by your context. A profile's year cannot be changed. Only the fields you supply are changed; supplying holidays REPLACES the profile's holiday list. Holiday dates must fall within the profile's year.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "update_holiday_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew profile name.
notesNoOptional free-text notes.
holidaysNoA JSON array (as a string) that REPLACES the profile's holidays, each: {"date":"YYYY-MM-DD","name":"...","full_day_off":true|false,"window_start":"HH:mm","window_end":"HH:mm"}. Dates must be within the profile's year.
is_activeNoWhether the profile is active.
profile_idYesId of the holiday profile to update (required). Must belong to your organization.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
default_for_countriesNoOptional comma-separated ISO-2 country codes this profile is the default for, e.g. "US,CA".

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 flag destructiveHint=true and idempotentHint=true, and the description goes well beyond them by specifying that supplying holidays REPLACES the entire list, that the year cannot be changed, and that only supplied fields are modified. These are exactly the destructive/partial-update semantics an agent needs before calling.

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?

Four tight sentences, front-loaded with the operation and scope, then the destructive replace rule and the year constraint. No filler or redundant restatement of the title.

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 7-parameter mutation with no output schema, the description covers partial-update semantics, the destructive replace behavior, and the year validation rule. It does not say what the response contains or what happens to dependent assignments when is_active is toggled, a minor remaining gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not carry: the profile's year is immutable and holiday dates must fall inside it, which constrains how holidays and default_for_countries can be used. It largely restates the schema's REPLACES wording, keeping it from a 5.

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 ('Update an existing holiday profile in your organization') and enumerates the mutable fields, which cleanly separates it from create_holiday_profile and delete_holiday_profile. An agent can identify the operation without opening the schema.

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 usage ('Update an existing...') and gives useful preconditions (year is immutable, only supplied fields change), but never explicitly names an alternative or states when to prefer create_holiday_profile or suggest_holiday_profile. Guidance is implied rather than spelled out.

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