Skip to main content
Glama

Units

list_units
Read-onlyIdempotent

Everything the venue rents by the night (rooms, homes, caravans, pitches) with price, capacity, beds, amenities and photos. Includes hidden units. 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": "list_units"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds genuinely new disclosure: hidden units are included in results, the populated fields are pre-announced (price, capacity, beds, amenities, photos), and the auth requirement plus single-venue scoping is spelled out. It does not mention pagination or result ordering, which keeps it from a 5.

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 sentences, both dense and front-loaded: the resource and its payload come first, then the scope fact (hidden units) and the auth requirement. Nothing is redundant with the title or with the annotations.

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 no output schema, the description is the only place that tells an agent what the response contains, and it does so explicitly. Required credentials and the single-venue constraint are stated. The remaining gap is behavioral detail about result size or pagination, which matters for a list tool that may return many units.

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 both parameters (address, access_key) are already documented in the schema and the baseline is 3. The description only restates that one venue is identified by its address and access key, adding no format, validation, or failure-mode detail beyond the structured fields.

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?

The description uses a clear verb+resource combination and enumerates the resource subtypes ("rooms, homes, caravans, pitches") along with the data returned (price, capacity, beds, amenities, photos). It also states a scope boundary ("Includes hidden units") and that the operation targets a single venue. It falls short of a 5 because it never names a sibling it differs from, and "list_stay_options" could plausibly be confused with this tool.

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?

Use is implied by "Everything the venue rents by the night," which tells an agent this is the inventory-retrieval tool for a venue. There is no explicit when-to-use, when-not-to-use, or guidance pointing to an alternative such as list_stay_options or list_nightly_prices, so routing between siblings 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