Skip to main content
Glama

Options for units and the listing

list_stay_options
Read-onlyIdempotent

The fixed lists used by the other tools: unit kinds, bed kinds, amenity keys for units and for the venue (with their English and Greek labels). 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_stay_options"
  }
}

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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine scope information: it acts on exactly one venue identified by address and access key, and returns bilingual labels. It still says nothing about output shape or whether the lists are stable across calls.

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 tight sentences: the returned content is front-loaded, then the venue scoping. No filler, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 source for return values; it names the list categories and mentions bilingual labels but does not say how they are keyed or structured. For a lookup tool this is adequate but leaves the agent guessing at response shape.

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% and the schema already explains that address is the name in name.bookare.app and access_key is the venue's key. The description restates the same scoping fact without adding format, validation, or error semantics, so the baseline 3 applies.

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 states a specific resource: the fixed enumeration lists (unit kinds, bed kinds, venue/unit amenity keys) with English and Greek labels. That distinguishes it from sibling list_* tools such as list_units, which return actual venue data rather than reference values. It does not explicitly name a sibling to contrast with, keeping it 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?

"The fixed lists used by the other tools" implies the use case — fetching valid key values before calling the other tools — but it never says so directly and names no alternatives or exclusions. An agent can infer the intent, yet nothing states when-not to use it.

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