Skip to main content
Glama

Liberdade

by io.github.junoventures

list_booking_services

List a venue's services — what it offers, with price and duration. Pass place_slug (from search_places) to list the services of a specific VENUE — a salon, clinic or studio listed in this directory; that is what you want in almost every case, and it is the only form whose serviceId works with create_booking. Omitting place_slug lists the directory site's own services instead, which most sites do not have. Returns name, description, price, duration in minutes, and bookableViaMcp. Services are listed for EVERY venue, including those with no online booking system — check bookableViaMcp: when it is false, id is null and you cannot book through create_booking, so point the user at bookingUrl or the venue's page instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
place_slugNoVenue place slug from search_places. Strongly recommended — without it you get the directory's own services, not a venue's.

TDQS

A4.9/5.0
Behavior5/5

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

No annotations exist, so description carries full burden. It details output fields (name, description, price, duration, bookableViaMcp) and explains behavior for non-bookable venues (id is null).

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?

The description is efficient but somewhat lengthy (three sentences, ~100 words). Front-loaded with main purpose, but could be slightly tighter without losing information.

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?

Given the tool's simplicity (one optional param, no output schema), the description covers all necessary information: purpose, parameter, output fields, and edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by explaining the parameter's purpose, source (search_places), and consequences of omission, enhancing the schema.

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?

The description clearly states it lists a venue's services with price and duration. It distinguishes between the two modes (with and without place_slug), which differentiates it from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says when to use place_slug ('what you want in almost every case') and when not, and provides alternative actions when bookableViaMcp is false.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Liberdade toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool targets a distinct domain (e.g., bookings, events, places, restaurants, movies, forms) with clear boundaries. Even similar actions like create_booking and request_reservation are differentiated by service type (appointment vs restaurant table) and payment flow.

Naming Consistency5/5

All 28 tools follow the consistent verb_noun snake_case pattern (e.g., create_booking, list_events, search_places). Verbs are appropriate and predictable, with no mixing of conventions.

Tool Count4/5

28 tools is slightly above the typical range, but each tool serves a distinct purpose within the comprehensive neighborhood directory domain. The count is justified by the breadth of features (booking, events, restaurants, movies, etc.).

Completeness4/5

The tool surface covers most user needs: searching, viewing details, booking, reservations, events, forms, and more. Minor gaps exist, such as no cancellation tools for bookings/reservations, but the core workflows are well-supported.

Resources