Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Toggle a holiday

toggle_holiday

Block or unblock one public holiday (holidayId from get_holiday_settings).

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": {
      "holidayId": "<holidayId>",
      "enabled": "<enabled>"
    },
    "name": "toggle_holiday"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
holidayIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive, open-world mutation, so the safety profile is carried by structured data. The description adds that it affects exactly one holiday and that the two directions are block vs unblock, but says nothing about effects on existing bookings, availability recalculation, or required permissions.

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 action and scope, with the provenance hint appended parenthetically. Nothing is redundant.

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?

For a mutation tool with two undocumented parameters, no output schema, and no parameter descriptions in the schema, the description leaves the meaning of 'enabled' and the effect on existing bookings/availability unstated. An agent could invoke it with the polarity inverted.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains where holidayId comes from but never clarifies what the boolean 'enabled' means (true = block or true = unblock), which is the single most important semantic for correct invocation.

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 verb pair (block/unblock) and resource (one public holiday), which is clearer than the generic 'toggle' in the name. It is distinguishable from update_holiday_settings and get_holiday_settings, though it doesn't explicitly contrast with them.

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?

Points the agent to get_holiday_settings as the source of holidayId, which is useful routing. However, it gives no when-to-use/when-not guidance versus update_holiday_settings or bulk holiday configuration, leaving selection partly implicit.

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

All Caly 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