Campo Belo

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

Name	Required	Description
`contact`	Yes	Who the booking is for. All three are required by the venue to confirm or reschedule.
`endDate`	Yes	Slot end as an ISO instant, exactly as returned by get_availability.
`serviceId`	Yes	Service ID from list_booking_services (called with the same place_slug).
`startDate`	Yes	Slot start as an ISO instant, exactly as returned by get_availability.
`place_slug`	Yes	Venue place slug from search_places.
`resourceId`	No	Optional staff/resource ID from the slot, when the user picked a specific professional.

TDQS

A5/5.0

Behavior5/5

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

No annotations provided, but description fully discloses key behaviors: nothing is booked until payment, returns checkout URL, slot re-validated, taken slot rejected, email not verified. 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?

Two paragraphs, front-loaded with critical payment gotcha, then usage order and constraints. Every sentence earns its place; no fluff.

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 tool complexity (6 params, nested object, no output schema), description covers purpose, output (checkout URL), preconditions, post-conditions, and caveats comprehensively.

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?

Schema coverage is 100%, but description adds contextual meaning beyond schema: dates must match get_availability, place_slug from search_places, contact fields required by venue. Adds significant value.

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 the resource 'appointment slot at a venue (Wix Bookings)', and distinguishes it from siblings by highlighting the payment step and checkout URL return.

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?

Provides explicit guidance: call get_availability before usage, inform user to open link, warns about slot re-validation and email verification. Clearly communicates when and how to use.

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

All Campo Belo 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 action on a specific resource (e.g., create_booking vs create_checkout vs reserve_event_tickets). Descriptions clearly differentiate purposes, and no two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_availability, list_categories, search_dishes). Verbs like get, list, create, request, rsvp are used uniformly, making the set predictable.

Tool Count4/5

28 tools is above the typical 3-15 range, but the server covers a broad domain (places, events, movies, booking, store, etc.). Each tool serves a clear purpose, so the count is justified for the scope.

Completeness4/5

The tool surface is extensive, covering searching, details, reviews, booking, events, menus, etc. Minor gaps exist (e.g., no cancel/update operations), but they are likely intentional given the user-facing nature of the server.

Resources

Need Help?