Pinheiros

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

Name	Required	Description	Default
`place_slug`	No	Venue 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

Behavior5/5

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

Fully discloses behavior: dual mode based on place_slug, that it returns all services even if not bookable, with null id when bookableViaMcp is false. No annotations to contradict, so description carries full burden and meets it.

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 verbose but well-structured: first sentence gives main purpose, then details. All sentences add value; no redundancy, but could be slightly more 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?

Given simple tool with one optional parameter, no output schema, and no annotations, description covers behavior, return fields, and edge cases (non-bookable services). Also provides error handling guidance.

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

Parameters4/5

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

Schema coverage is 100% with description for place_slug. Description adds value by noting source (search_places), strong recommendation, and behavioral consequence of omission, enhancing understanding beyond 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, and distinguishes between using place_slug (venue services) vs. omitting (directory's own services). This differentiates it from siblings like list_products or list_offers.

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?

Gives explicit guidance: pass place_slug in most cases, omitting yields directory services rarely, and only venue services work with create_booking. Also advises checking bookableViaMcp and falling back to bookingUrl.

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

All Pinheiros tools Inspect

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

Disambiguation5/5

Each tool targets a distinct operation: bookings, restaurants, events, forms, etc. Even similar actions like create_booking and request_reservation are clearly differentiated by domain and description.

Naming Consistency5/5

Tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_blog_posts). Collection retrieval uses list_ while single item uses get_, which is a standard and clear convention.

Tool Count4/5

28 tools is on the upper end, but each serves a distinct function for a comprehensive neighborhood directory (places, events, booking, forms, etc.). No obvious bloat given the scope.

Completeness5/5

The tool surface covers all major user intents for a local directory: searching places, getting menus, booking services, viewing events, submitting forms, etc. No critical gaps are apparent.

Resources

Need Help?