Skip to main content
Glama

Coline

Delete scheduling link

delete_scheduling_link
DestructiveIdempotent

Deletes a scheduling link; nobody can book through it any more. Bookings already made stay.

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": {
      "workspace": "<workspace>",
      "linkId": "<linkId>"
    },
    "name": "delete_scheduling_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYesScheduling link id from list_scheduling_links.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds real value by scoping the destruction: the link stops accepting bookings but existing bookings survive, which is the key behavioral detail an agent needs before calling it. It stops short of stating irreversibility or permission requirements.

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 short sentences, no filler, with the primary effect front-loaded and the retention caveat second. Every clause carries information.

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?

An output schema exists, so return values need no explanation, and the description covers the essential side-effect semantics for a destructive single-resource tool. Only minor gaps remain: no statement that deletion is permanent/irreversible and no mention of auth or permission requirements.

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%, with both linkId and workspace documented in the schema, including provenance (list_scheduling_links, workspaces.list). The description adds no additional parameter meaning, so the baseline of 3 applies.

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 ("Deletes a scheduling link") and immediately clarifies the resulting state ("nobody can book through it any more"), which cleanly separates it from update_scheduling_link or get_scheduling_link. An agent can identify the operation and its effect 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?

Usage is implied by the destructive framing, but the description never states when to delete versus when to update or deactivate a link, nor any prerequisite such as confirming the caller owns the link. It gives no explicit alternative among the scheduling-link siblings.

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