Skip to main content
Glama

Delete a unit

delete_unit
Destructive

Deletes a unit together with its photos. A unit that has ever had a booking is not deleted: it is hidden from guests instead, so the booking history stays. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "unit_id": "<unit_id>"
    },
    "name": "delete_unit"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idYes
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: photos are cascaded, and units with any past booking are hidden rather than deleted to preserve history. It stops short of saying what the response reports or whether the hide is reversible.

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?

Three short sentences, front-loaded with the primary effect and the critical exception. The closing sentence on venue scoping is largely a restatement of the schema fields, so it earns slightly less than full marks.

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 three-parameter mutation with no output schema, the description covers the important unknowns: cascade scope, the hidden-instead-of-deleted exception, and per-venue targeting. Only the return value distinguishing 'deleted' from 'hidden' is left unaddressed.

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 67%, with address and access_key already documented in the schema. The description restates the venue/address+key scoping but adds no format or semantics for unit_id, the one parameter left undocumented in the schema.

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 unit") and immediately scopes the effect ("together with its photos"), plus clarifies it operates on a single venue. An agent can distinguish this from siblings like update_unit or delete_pack without opening any 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 name and confirmed by the description: this is how you remove a unit. The booking-history fallback explains what happens when deletion isn't possible, which is useful conditional context, but there is no explicit routing guidance to siblings (e.g. when to hide vs. update instead).

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