Skip to main content
Glama

Filipe Coffee

by io.github.junoventures

create_booking

Book an appointment slot at a venue (Wix Bookings). NOTHING IS BOOKED UNTIL THE CUSTOMER PAYS: this returns a checkout URL, and the booking stays off the venue's calendar until a human opens that URL and completes payment on the venue's own site. Tell the user they must open the link. Call get_availability immediately before this — the slot is re-validated server-side and a taken slot is rejected. The contact email is NOT verified at this step; the checkout is what confirms it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactYesWho the booking is for. All three are required by the venue to confirm or reschedule.
endDateYesSlot end as an ISO instant, exactly as returned by get_availability.
serviceIdYesService ID from list_booking_services (called with the same place_slug).
startDateYesSlot start as an ISO instant, exactly as returned by get_availability.
place_slugYesVenue place slug from search_places.
resourceIdNoOptional staff/resource ID from the slot, when the user picked a specific professional.

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: payment required first, checkout URL returned, booking stays off calendar, email not verified at this step, and slot re-validation. No contradictions.

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?

Three sentences packed with essential information, front-loaded with the critical payment caveat. No redundant words; every sentence adds value.

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?

Covers preconditions (get_availability call), postconditions (checkout URL), and caveats (payment needed, slot re-validation, email not verified). Adequate given no output schema.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., contact fields are required by venue), but mainly focuses on overall flow rather than parameter details.

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 books an appointment slot at a venue (Wix Bookings) and explicitly distinguishes that nothing is booked until payment, thus differentiating it from related tools like get_availability and create_checkout.

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 instructs to call get_availability immediately before, and advises telling the user to open the checkout link. Provides clear when-to-use context and what to expect, including server-side slot validation.

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

All Filipe Coffee 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
Disambiguation5/5

Each tool targets a distinct resource or action (e.g., bookings, events, places, menus, forms), with detailed descriptions that clearly differentiate even similar operations like create_booking vs. reserve_event_tickets. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using lowercase and underscores (e.g., create_booking, get_availability, list_events). Verbs are semantically appropriate (create, get, list, search, submit) and predictable.

Tool Count4/5

28 tools is slightly above the typical 3-15 range, but the breadth of the neighborhood directory domain justifies each tool. The count feels dense but not excessive, with no redundant tools.

Completeness5/5

The tool set covers the full lifecycle of a neighborhood directory: place search, restaurant menus, events, movie showtimes, booking, reviews, blog, guides, offers, loyalty, forms, and profiles. Obvious gaps like review creation are absent but likely out of scope.

Resources