Skip to main content
Glama

Release a held time

release_hold
DestructiveIdempotent

Use this when the person no longer wants a time you held for them and has not confirmed it. Ends the hold at once, so the time is free again. Do not use for cancelling a confirmed booking: release_hold only ends a hold that is still waiting, and the person cancels a booking with the business.

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": {
      "holdId": "<holdId>"
    },
    "name": "release_hold"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdIdYesThe holdId hold_booking answered with.
languageNoThe language to answer in (BCP 47).

Output Schema

NameRequiredDescriptionDefault
metaYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 adds real value by explaining what the destruction means operationally: the hold ends immediately and the time becomes free again. It stops short of covering failure modes such as an already-expired or already-confirmed hold, which is the remaining gap.

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?

The when-to-use condition is front-loaded and the exclusion follows immediately, so an agent gets the decision rule in the first lines. The third sentence partially restates the second ('only ends a hold that is still waiting'), which is mild redundancy but not harmful.

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?

With annotations covering mutability and idempotency and an output schema covering return values, the description supplies the state precondition that matters. It could go further on what happens if the hold was already confirmed or has lapsed, but the essential calling information is present.

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 coverage is 100%, including the note that holdId is the value hold_booking returned, so the schema carries the parameter meaning. The description adds no further detail on holdId format or on the optional language parameter, which is the expected baseline when the schema is this complete.

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 ('ends the hold', 'so the time is free again') and immediately scopes it as releasing an unconfirmed hold rather than cancelling a booking. An agent can distinguish it from confirm_booking and get_booking_status from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use trigger ('the person no longer wants a time you held for them and has not confirmed it') paired with an explicit when-not ('Do not use for cancelling a confirmed booking') and the reason the boundary exists. Nothing is left to inference.

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