Skip to main content
Glama

Agenda SP

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?

Discloses that services are listed for every venue including those without online booking, and explains how to check bookableViaMcp. Also notes that id is null when not bookable, and directs to bookingUrl as fallback. No annotations present, so description fully bears the transparency burden and does so thoroughly.

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?

Description is five sentences packed with information. While no word is wasted, the density could be slightly improved by splitting into bullet points or shorter sentences for easier scanning. Still very concise overall.

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?

Despite no output schema, the description enumerates return fields and explains their implications for booking. Also connects to sibling tools search_places and create_booking. Covers all essential context for such a simple tool.

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 already has a good description for place_slug, but the tool description adds critical context: origin from search_places, typical use case, and relationship to create_booking. This significantly enhances understanding beyond the schema alone.

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?

Description clearly states the tool lists a venue's services with verb 'list' and resource 'services'. It distinguishes between venue services and directory services, and lists output fields. Purpose is precise and unambiguous.

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 to pass place_slug for venue services, which is the intended use, and warns that omitting it returns directory services which most sites lack. Provides clear when-to-use and when-not-to-use guidance.

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

All Agenda SP 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.1/5.0
Disambiguation4/5

Tools are mostly distinct with clear descriptions. Some overlap in actions that require user to click a link (create_booking, create_checkout, request_reservation, etc.), but each targets a different domain (booking, store, restaurant, event tickets, RSVP). Minor ambiguity possible but descriptions clarify.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_availability, search_places). No deviations or mixed conventions.

Tool Count4/5

28 tools is slightly high for a neighborhood directory, but each serves a specific function (search, booking, events, movies, offers, etc.). The scope justifies the count, though some tools like list_blog_posts and list_faqs might be considered niche.

Completeness4/5

The tool set covers search, place details, categories, menus, events, movies, offers, booking, and forms. Missing update/delete operations for places or user management, but these are likely out of scope for a read-only directory. Core queries and actions are well-supported.

Resources