Skip to main content
Glama
Sign In

Caly

by com.trycaly
OverviewDiscussionsAdmin

Delete private link

delete_private_link
Destructive

Delete a private booking link; anyone holding it can no longer book. 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": {
      "eventTypeId": "<eventTypeId>",
      "linkId": "<linkId>"
    },
    "name": "delete_private_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYesPrivate link id from list_private_links.
eventTypeIdYesNumeric event type ID, as returned by list_event_types.
confirmTokenNoLeave empty on the first call. Then pass the token from the CONFIRMATION_REQUIRED answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes beyond them by disclosing the concrete user-facing consequence and the mandatory two-call confirmation flow with CONFIRMATION_REQUIRED and confirmToken. It stops short of stating that deletion is permanent/irreversible, which would complete the picture.

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?

Two tight sentences: consequence first, then the procedure. No filler, and the critical destructive effect is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description covers the one non-obvious return path (CONFIRMATION_REQUIRED plus confirmToken) and the required follow-up call, so an agent can complete the operation correctly without guessing.

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 sequencing semantics the schema only hints at: the token must be supplied with the SAME arguments on the retry, and the agent must tell the user what will happen first. That is real meaning beyond the field-level text.

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 and resource ('Delete a private booking link') and adds the resulting scope ('anyone holding it can no longer book'), which distinguishes it from update_private_link and list_private_links. It does not explicitly name the sibling alternative, so it falls short of a 5.

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?

Gives clear procedural guidance for the confirmation handshake, but says nothing about when to delete versus when to disable/rescope a link via update_private_link, nor any preconditions such as ownership or permissions. Usage context is implied rather than stated.

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