Skip to main content
Glama

Get booking choices

get_booking_choices
Read-onlyIdempotent

The choices the booking lightbox offers for one option_id. Without a clinic: every clinic that can book it, with distance, practitioner count and prices. With clinic_id: the practitioners with their own prices (practitioner_id), add-ons, packages, party size, cancellation notice and payment methods.

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": {
      "option_id": "<option_id>"
    },
    "name": "get_booking_choices"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoA position. It wins over place.
placeNoA town or place name ("Asker", "Lierskogen") or a four-digit postal code ("3420").
localeNoAnswer language: nb (Norwegian) or en.nb
clinic_idNoThe clinic_id find_clinics returns. Never build it from a name. A clinic site needs none.
option_idYesThe option_id get_treatment returns.

Output Schema

NameRequiredDescriptionDefault
placeYes
add_onsYes
clinicsYes
completeYesfalse: some clinics or practitioners are still building.
packagesYes
clinic_idYes
option_idYes
party_sizeYes
booking_urlYes
option_nameYes
treatment_idYes
practitionersYes
payment_methodsYes
possible_extrasYesExtras the provider may add during the visit, at these prices; never chosen when booking.
cancellation_notice_hoursYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / add_ons / items / properties / overlaps_other_add_ons
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / add_ons / items / required
      Previous value: -[
      -  "add_on_id",
      -  "name",
      -  "price_nok",
      -  "extra_minutes",
      -  "practitioner_ids"
      -]New value: +[
      +  "add_on_id",
      +  "name",
      +  "price_nok",
      +  "extra_minutes",
      +  "overlaps_other_add_ons",
      +  "practitioner_ids"
      +]
  2. Changed2 schema fields changed
    • addedOutput schema / properties / add_ons / items / properties / practitioner_ids
      Added value: +{
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / add_ons / items / required
      Previous value: -[
      -  "add_on_id",
      -  "name",
      -  "price_nok",
      -  "extra_minutes"
      -]New value: +[
      +  "add_on_id",
      +  "name",
      +  "price_nok",
      +  "extra_minutes",
      +  "practitioner_ids"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / possible_extras
      Added value: +{
      +  "description": "Extras the provider may add during the visit, at these prices; never chosen when booking.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "name": {
      +        "type": "string"
      +      },
      +      "price_nok": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "price_nok"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "option_id",
      -  "option_name",
      -  "treatment_id",
      -  "clinic_id",
      -  "complete",
      -  "clinics",
      -  "practitioners",
      -  "add_ons",
      -  "packages",
      -  "party_size",
      -  "cancellation_notice_hours",
      -  "payment_methods",
      -  "booking_url",
      -  "place"
      -]New value: +[
      +  "option_id",
      +  "option_name",
      +  "treatment_id",
      +  "clinic_id",
      +  "complete",
      +  "clinics",
      +  "practitioners",
      +  "add_ons",
      +  "possible_extras",
      +  "packages",
      +  "party_size",
      +  "cancellation_notice_hours",
      +  "payment_methods",
      +  "booking_url",
      +  "place"
      +]
  4. First observed

TDQS

A3.8/5.0
Behavior4/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 behavioral context beyond that: the response shape changes based on whether clinic_id is supplied, and it enumerates what appears in each mode (distance, practitioner count, prices, add-ons, packages, party size, cancellation notice, payment methods).

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 one-line purpose before branching into the two modes. Dense and largely waste-free, with only the parenthetical '(practitioner_id)' feeling like schema-level detail repeated in prose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and full annotation coverage, the description only needed to explain the mode-dependent result and the scoping constraint, and it does both. An agent can call this correctly from the description plus structured fields without further clarification.

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 100%, so the baseline is 3 and the schema already documents near/place/locale and even hints that a clinic site needs no clinic_id. The description adds the key semantic of clinic_id's presence/absence switching result modes, but says nothing about near, place or locale and their interaction, so it only marginally exceeds the schema.

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 names the specific resource ('the choices the booking lightbox offers for one option_id') and immediately defines the two result modes keyed on clinic_id. It is clear what the tool returns, though it never contrasts itself with adjacent tools like find_clinics or find_practitioners, so sibling differentiation is left to inference.

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?

'Without a clinic: ... With clinic_id: ...' gives real conditional guidance on how to drive the two modes, which is more than most definitions offer. However, it never says when to reach for this tool instead of find_clinics or find_practitioners, and gives no exclusions or prerequisites, so usage is implied rather than prescribed.

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