Skip to main content
Glama

Add a unit

create_unit

Adds something the venue rents by the night: a room, apartment, home, caravan, glamping tent or pitch. For several identical ones (e.g. 20 pitches) create one unit and set identical_units. Guests can see and book it straight away unless shown_to_guests or takes_bookings is false. 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>",
      "name": "<name>",
      "kind": "<kind>",
      "price_per_night_eur": "<price_per_night_eur>"
    },
    "name": "create_unit"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedsNoHow many beds of each kind, e.g. {"double":1,"single":2}. Kinds: double, single, sofa, bunk.
kindYesWhat it is.
nameYesName guests see, e.g. "Sea-view studio" or "Tent or camper pitch".
addressYesThe venue’s address name, the "name" in name.bookare.app.
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_eurYesBase price per night in euro (seasons can override it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: the unit goes live and bookable immediately unless shown_to_guests or takes_bookings is false, and takes_bookings=false also closes its nights on connected channels while the venue can still add its own bookings. That is valuable, but the annotations already flag this as a non-readOnly, non-destructive, non-idempotent mutation, and the description never says that repeated calls create duplicate units or what the call returns.

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 sentences, front-loaded with the resource definition, then the multi-unit shortcut, then the visibility side effect, then the venue scoping. Dense and mostly waste-free, though the identical_units sentence overlaps the schema description.

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?

Covers the creation semantics, default visibility, and the venue-addressing requirement for a 16-parameter mutation, but with no output schema the description never indicates what comes back (e.g. the new unit's identifier), and it gives no indication of prerequisite errors or permission failures. That leaves a modest gap for an agent that needs to chain into update_unit afterwards.

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%, so every one of the 16 parameters is already documented in the input schema, including identical_units and the two visibility flags. The description's mention of identical_units (20 pitches) and the visibility behavior largely restates schema text, so it adds little parameter meaning beyond the baseline.

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 ("Adds something the venue rents by the night") and enumerates the concrete kinds (room, apartment, home, caravan, glamping tent, pitch), which lets an agent immediately separate it from delete_unit/update_unit and from create_venue or create_class_type 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 Guidelines4/5

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

Gives a clear creation-time rule: for many identical items create one unit and set identical_units rather than N units, which is exactly the decision an agent would otherwise get wrong. It does not name the update/delete siblings as the route for changing or removing an existing unit, so the exclusion side 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources