Skip to main content
Glama

Change a unit

update_unit

Changes a unit. Only the fields you send change. Existing bookings keep their agreed total. 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": "update_unit"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedsNoHow many beds of each kind, e.g. {"double":1,"single":2}. Kinds: double, single, sofa, bunk.
kindNoWhat it is.
nameNoName guests see, e.g. "Sea-view studio" or "Tent or camper pitch".
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idYes
bedroomsNo0 = not shown.
size_sqmNoSize in square metres. 0 = not shown.
amenitiesNoUnit amenity keys (the unit_amenities list of this venue’s stay options), e.g. ["wifi","ac","kitchen"].
bathroomsNo0 = not shown.
access_keyYesThe venue’s access key.
min_nightsNoMinimum nights per booking. Default 1.
descriptionNoFree text for guests (up to 600 characters).
guests_up_toNoMost guests it takes (1-60).
takes_bookingsNoFalse keeps the unit visible to guests but they cannot book it (e.g. not ready yet); its nights are closed on connected channels too. The venue can still add bookings itself. Default true.
identical_unitsNoHow many identical ones exist, e.g. 20 tent and camper pitches. Default 1.
shown_to_guestsNoFalse hides the unit from the booking page. Default true.
price_per_night_eurNoBase price per night in euro (seasons can override it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's job is to add what annotations cannot. It does: partial-update semantics, the non-obvious side effect that existing bookings keep their agreed total, and the venue-scoping requirement. Return shape and failure modes are still unstated.

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?

Four short sentences, each adding something: purpose, partial-update rule, booking-price guarantee, venue scoping. The opening "Changes a unit" mildly restates the title, which is the only wasted phrasing.

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 17-parameter mutation with no output schema, the description covers the two things an agent most needs beyond the schema: that omitted fields are left alone and that booking totals are not recalculated. It does not describe the response or whether partial failures roll back, which keeps it below 5.

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 94% and the per-field descriptions are rich (defaults, ranges, 0 = not shown), so the schema carries nearly all parameter meaning. The description only adds the address/access_key scoping hint, which the schema already documents. Baseline 3 is appropriate.

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 ("Changes a unit") and immediately qualifies it with partial-update scope, so an agent can distinguish it from create_unit/delete_unit. It stops short of naming a sibling explicitly, so it lands at 4 rather than 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?

"Only the fields you send change" gives useful patch-style guidance about how to call it, and "Acts on one venue" implies the address/access_key scoping. However, there is no explicit statement of when to prefer this over update_venue or create_unit, and no exclusions or prerequisites.

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