Caly

Delete schedule

delete_schedule

Destructive

Delete an availability schedule. Event types using it fall back to the default schedule. Two steps: the first call returns CONFIRMATION_REQUIRED with a confirmToken; tell the user what will happen, then call again with the SAME arguments plus confirmToken.

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": {
      "scheduleId": "<scheduleId>"
    },
    "name": "delete_schedule"
  }
}

Input Schema

Name	Required	Description	Default
`scheduleId`	Yes	Schedule id from list_schedules.
`confirmToken`	No	Leave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructive=true and idempotent=false, but the description goes further by disclosing the actual side effect (event types fall back to the default schedule) and the human-in-the-loop confirmation handshake. That is exactly the extra context an agent needs before a destructive call.

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?

Three short sentences, zero filler, with the destructive consequence and the confirm protocol front-loaded ahead of the mechanics. Every sentence earns its place.

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?

Covers purpose, side effect and the confirmation flow for a destructive two-parameter tool with no output schema. Minor gaps remain (token expiry/abort behavior, error case for an unknown scheduleId), but nothing that would cause a misinvocation in normal use.

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 both parameters are already documented. The description still adds meaning by making explicit that the second call must reuse the SAME arguments plus confirmToken, reinforcing that the token is additive rather than a replacement.

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+resource ("Delete an availability schedule") and immediately names the downstream effect on event types. Clearly distinct from the many sibling delete_* tools and from update_schedule/duplicate_schedule.

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 two-step confirm protocol is spelled out precisely: first call returns CONFIRMATION_REQUIRED with a confirmToken, tell the user, then re-call with the same args plus the token. That is strong operative guidance, though it never states when to prefer delete_schedule over alternatives (e.g. bulk_set_default_availability) or what to do if the schedule is the default.

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

All Caly tools Inspect

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

Need Help?