Skip to main content
Glama

Vila Mariana

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

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

With no annotations provided, the description fully discloses behavioral traits: the tool returns a checkout URL, does not finalize booking, server-side re-validates the slot, and contact email is unverified. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose, but the dense paragraph style could be improved with bullet points for readability. Nevertheless, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers all necessary behavioral aspects: preconditions, payment flow, server-side validation. However, it lacks explicit mention of the return value format (though it implies a checkout URL). Adequate given the tool's complexity.

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 description coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema (e.g., 'All three are required by the venue'), but does not significantly enhance parameter understanding.

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 the verb 'Book' and resource 'appointment slot at a venue (Wix Bookings)', distinguishing it from siblings like 'create_checkout' or 'request_reservation'.

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 directs to call 'get_availability' immediately before, explains the payment flow (returns checkout URL, nothing booked until payment), and instructs the user to open the link. Also notes that contact email is not verified.

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

All Vila Mariana 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 action and resource: booking appointments, restaurant reservations, event tickets, searches, etc. No two tools have overlapping purposes; even similar actions like create_booking and request_reservation are for different domains (appointments vs. restaurant tables).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using lowercase and underscores (e.g., get_availability, list_events, create_booking). There is no mixing of styles like camelCase or inconsistent verbs.

Tool Count4/5

28 tools is above the typical well-scoped range but each tool serves a clear purpose within the comprehensive neighborhood directory domain. The count feels justified, though slightly heavy.

Completeness4/5

The tool set covers most major features of a neighborhood directory: places, events, booking, restaurant menus, reviews, forms, etc. Minor gaps exist, such as no create_review or update operations, but core workflows are complete.

Resources