Skip to main content
Glama

Agenda Rio

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 all venues even without online booking, explains the bookableViaMcp field and its implications, and lists returned fields. With no annotations, the description thoroughly covers behavioral traits.

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 a single paragraph that is well-organized and front-loaded. It could be slightly tighter, but it efficiently conveys all necessary information without redundancy.

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?

With no output schema, the description compensates by listing returned fields and explaining the bookableViaMcp behavior. It fully addresses the tool's complexity and expected usage scenarios.

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 schema has 100% coverage, but the description adds critical context: the effect of omitting place_slug, its relationship with create_booking, and the recommendation to use it. This goes beyond what the schema provides.

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, and distinguishes between listing venue services (with place_slug) and directory services (without place_slug), making the tool's specific purpose 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?

Explicit guidance on when to use with place_slug (almost always, required for create_booking) and when to omit (rarely, directory's own services). Also warns about venues with no online booking and how to handle them.

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

All Agenda Rio 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

Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Overlaps like create_booking vs request_reservation are clarified by domain (appointments vs restaurant) and mechanics.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_places). The same conjugation style (snake_case) is used throughout, with no mixing of conventions.

Tool Count4/5

At 28 tools, the set is slightly larger than the typical well-scoped range (3-15), but each tool corresponds to a distinct feature of the neighborhood directory, making the count reasonable for the breadth of functionality.

Completeness5/5

The tool surface covers all major user-facing actions: searching, browsing, booking, purchasing, and retrieving information. No obvious gaps exist for the stated purpose of a neighborhood directory.

Resources