Skip to main content
Glama

Itaim Bibi

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?

With no annotations, the description fully discloses behavioral traits: it lists all venues even without online booking, explains the bookableViaMcp flag, null ID, and fallback to bookingUrl. This goes beyond a simple listing to provide actionable context.

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 informative but slightly verbose; some sentences could be merged. However, every sentence adds value, and the main purpose is front-loaded. It is effective but not maximally concise.

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?

For a tool with no output schema, the description explains all relevant return fields (name, description, price, duration, bookableViaMcp) and provides complete guidance on interpreting results, including what to do when services are not bookable.

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?

Although schema coverage is 100%, the description adds significant meaning by explaining the two modes (with/without place_slug) and linking to search_places. It clarifies that place_slug is the only form compatible with create_booking, which the schema alone does not convey.

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 that the tool lists a venue's services with price and duration, distinguishing between venue-specific services (with place_slug) and directory-wide services (without place_slug). This specific verb-resource combination is distinct among siblings.

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?

The description explicitly explains when to use place_slug (for venue services, which works with create_booking) and when to omit it (directory's own services, rarely present). It also provides guidance on handling non-bookable services via bookableViaMcp.

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

All Itaim Bibi 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.2/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: appointments, products, events, places, menus, reviews, forms, etc. No two tools have overlapping purposes; even similar booking tools (create_booking, request_reservation, reserve_event_tickets, rsvp_event) are clearly differentiated by description and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_booking, list_events, search_places). Verbs are appropriate (create, get, list, search, submit, request, reserve, rsvp) and nouns clearly indicate the resource.

Tool Count4/5

28 tools cover a broad domain (neighborhood directory with Wix integrations). While each tool has a clear purpose, the count exceeds the typical 3-15 range slightly, making the surface feel somewhat heavy but still manageable.

Completeness5/5

The tool surface provides comprehensive coverage for the domain: discovery (search places, list events, list guides), details (get place, get reviews), booking (appointments, restaurant, event tickets, RSVP), checkout, forms, FAQs, loyalty, pricing plans, and more. No obvious dead ends for common user journeys.

Resources