Skip to main content
Glama

Genesis Social

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

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

Since no annotations are provided, the description carries the full burden. It discloses key behaviors: listing services, the effect of place_slug, the meaning of bookableViaMcp (false means id is null, cannot book via create_booking). It does not explicitly state that it is read-only, but that is implied. A 4 is appropriate as it covers the most important behavioral aspects.

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?

The description is a single paragraph of about 5 sentences, each providing essential information. It is front-loaded with the main purpose and concise without being terse. No unnecessary words.

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 no output schema, the description compensates by listing return fields (name, description, price, duration, bookableViaMcp) and explaining the non-bookable case. It fully covers the tool's functionality and provides guidance for handling 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?

The description adds significant context beyond the schema: it explains that place_slug comes from search_places, that it gives venue services which are the only ones with serviceId working for create_booking, and that omitting gives directory services. With 100% schema coverage, the description still enhances understanding greatly.

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. It distinguishes between two modes: with place_slug (venue services) and without (directory's own services). The verb 'list' and resource 'venue's services' are explicit.

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 provides explicit guidance: pass place_slug to get venue services (almost always desired), omitting gets directory services (rarely present). It also advises what to do when bookableViaMcp is false, directing to bookingUrl or venue page.

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

All Genesis Social 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 action and domain, with clear descriptions preventing confusion. Similar tools like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are differentiated by service type and workflow.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_categories), ensuring predictability and ease of use for agents.

Tool Count4/5

With 28 tools, the set is fairly large but appropriate for a comprehensive neighborhood directory covering multiple domains (places, events, booking, store, forms, etc.). Each tool serves a distinct purpose without redundancy.

Completeness5/5

The tool surface covers the full lifecycle of common user needs: search and discovery, detailed info, reservations, purchases, and interactions (forms, FAQs). No obvious gaps for the described purpose of a neighborhood directory.

Resources