Skip to main content
Glama

Services and prices

list_services
Read-onlyIdempotent

Use this when you know the business and the person wants to see what it offers. Returns each service's name, description, length and price, any deposit, and how it is booked: bookVia assistant means a time can be held here, and bookVia website means the person books on the business's own page at bookingPageUrl. bookVia says how each one is reached: assistant, website or enquiry. A trip also has days, perPerson and maxPeople. Filter with query or category, or pick a branch with locationId. Do not use for health or medical treatments: businesses that offer them are not on this server. For a business that shows trips, the words in its trips are not read for this; its kind of business and everything else on its account still are.

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": {
      "business": "<business>"
    },
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1 to 50, 20 when not given.
queryNoWords to look for in a service's name, category or description.
businessYesThe business: its bookatu.com link or its own domain on Bookatu, or its slug.
categoryNo
languageNoThe language to answer in (BCP 47).
locationIdNoA branch of the business.
clientTimeZoneNoThe client's IANA time zone, such as America/Toronto. Ask for their city when unsure.

Output Schema

NameRequiredDescriptionDefault
metaYes
moreYes
businessYes
servicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / business / description
      Previous value: -"The business: its Bookatu name (slug), a bookatu.com link to it, or its own website address."New value: +"The business: its bookatu.com link or its own domain on Bookatu, or its slug."
    • changedOutput schema / properties / services / items / properties / bookVia / description
      Previous value: -"assistant: a time can be held here. website: the client books on the business's booking page."New value: +"assistant: a time can be held here. website: the client books on the business's booking page. enquiry: the person asks the business with send_enquiry."
    • changedOutput schema / properties / services / items / properties / bookVia / enum
      Previous value: -[
      -  "assistant",
      -  "website"
      -]New value: +[
      +  "assistant",
      +  "website",
      +  "enquiry"
      +]
    • addedOutput schema / properties / services / items / properties / days
      Added value: +{
      +  "description": "A trip's length in whole days.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / services / items / properties / maxPeople
      Added value: +{
      +  "description": "The most people an enquiry about this trip can name.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / services / items / properties / perPerson
      Added value: +{
      +  "description": "The price is for each person, not the whole group.",
      +  "type": "boolean"
      +}
  2. 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 and non-open-world, so the bar is lower, yet the description still adds real substance: what fields come back, what bookVia values mean for each route, that trips carry days/perPerson/maxPeople, and that trip wording is excluded from search. It omits pagination behaviour and the default page size, which the schema covers only partially.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger and return-value sentences are front-loaded and useful, but the bookVia explanation is repetitive (it states how booking is reached twice) and the closing sentence about trips ('the words in its trips are not read for this; its kind of business and everything else on its account still are') is convoluted and hard to parse.

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 an output schema present and strong annotation coverage, the description is complete enough to call correctly: it names the required business input, the filter options, exclusions, and the shape of returned records. Only pagination and empty-result behaviour are left implicit.

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 86%, so the baseline is 3. The description adds only mild meaning by grouping query/category as filters and locationId as branch selection, without explaining matching behaviour or how limit or language interact with results.

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 opening sentence states the situation and the resource ('the person wants to see what it offers') and the body confirms it returns each service's name, description, length, price, deposit and booking route. It is clearly differentiated from booking-flow siblings, though it never names an alternative tool like get_business for account-level details.

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?

It gives explicit trigger context ('when you know the business and the person wants to see what it offers') plus a hard exclusion: do not use for health or medical treatments because those businesses are not on this server. It also explains the two filtering axes, but stops short of naming a sibling to use instead when a business is not known.

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