Skip to main content
Glama

MONO Social

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?

No annotations provided, but description thoroughly discloses key behaviors: returns a checkout URL, slot re-validation server-side, email not verified, and that the booking stays off the calendar until payment. This fully covers behavioral transparency.

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?

Single paragraph, well-structured with critical warning front-loaded. Every sentence adds value; could be slightly more concise but efficient overall.

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?

Given 6 parameters (1 optional), nested objects, and no output schema, the description covers the process, prerequisites, and key behaviors. Missing return format and error conditions, but otherwise quite complete.

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%, so baseline 3. Description adds value beyond schema by noting that contact email is not verified, all contact fields are required by venue, dates must be used exactly as from get_availability, and resourceId is for specific professional. Justifies a 4.

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?

Clearly states 'Book an appointment slot at a venue (Wix Bookings)' with specific verb and resource. Distinguishes itself by explaining that booking is not final until payment via checkout URL, differentiating from simple booking tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/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 to inform the user they must open the link. Provides clear context but lacks explicit alternatives for situations where payment is not needed.

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

All MONO Social 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 domain action, with clear boundaries between similar operations (e.g., create_booking vs request_reservation vs reserve_event_tickets). Descriptions provide enough context to avoid confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_booking, get_availability, list_events. No mixing of styles or ambiguous verbs.

Tool Count4/5

28 tools is slightly above average but appropriate for a multi-feature neighborhood directory covering bookings, events, movies, menus, forms, etc. Each tool serves a distinct purpose, justifying the count.

Completeness4/5

The tool set covers most expected operations for a directory site: search, details, reviews, booking, events, menus, blog, FAQ, forms, etc. Minor gaps like cancellation or user booking history are acceptable given the domain scope.

Resources