Skip to main content
Glama

Delete calendar pause

delete_calendar_pause
Destructive

Lift a pause or a day off of a project's calendar: its occurrences are back, each as its rule and its own changes say. Anybody who may write in the project.

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": {
      "project": "<project>",
      "pauseId": "<pauseId>"
    },
    "name": "delete_calendar_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
pauseIdYesThe pause, as list_calendar_pauses gives 'id'.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not carrying the safety burden alone. It nonetheless adds real behavioral context beyond them: the pause's occurrences return, each restored according to its rule and its own per-occurrence changes, and it states the write-permission requirement. It stops short of saying whether the deletion is reversible or how restored occurrences interact with existing conflicts.

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?

Two short sentences with the action front-loaded and no filler. The phrase 'each as its rule and its own changes say' is slightly elliptical but conveys the restoration semantics compactly.

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 destructive two-parameter tool with full schema coverage and annotations covering the destructive profile, the description supplies the effect of deletion and the permission gate. Edge cases such as an invalid or already-deleted pauseId are not addressed, but no output schema is needed here and the core picture is complete.

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 description coverage is 100% — project is documented with an example key and pauseId is tied to list_calendar_pauses 'id'. The description adds no further meaning to either parameter, so the baseline 3 applies.

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?

The description uses a concrete verb ('Lift') on a specific resource ('a pause or a day off of a project's calendar'), so the agent knows this removes a calendar pause rather than editing one. It does not explicitly name the sibling set_calendar_pause, but the removal semantics are unambiguous.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named (e.g., set_calendar_pause to modify, list_calendar_pauses to obtain the id). The only conditional statement is a permission note ('Anybody who may write in the project'), which is authorization, not usage guidance.

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