Vila Madalena

get_availability

Get available time slots for a bookable service on a given date (Wix Bookings). Pass the serviceId from list_booking_services and a date in YYYY-MM-DD. Pass the same place_slug you used there — slot times are returned in the VENUE's timezone, which is not necessarily the directory's.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format (e.g. "2026-06-25").
`serviceId`	Yes	Service ID from list_booking_services.
`place_slug`	No	Venue place slug — use the same one passed to list_booking_services.

TDQS

A4.3/5.0

Behavior4/5

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

Discloses a key behavioral trait: returned slot times are in the venue's timezone, not necessarily the directory's. No annotations provided, so description carries full burden. 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 sentences, front-loaded with purpose, followed by critical usage details. No unnecessary words.

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

Completeness3/5

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

Covers usage and a behavioral nuance, but does not describe the return structure of available time slots. Given moderate complexity (3 params, no output schema), the description is adequate but incomplete.

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?

Parameters are fully described in schema (100% coverage). Description adds value by clarifying the cross-tool dependency (serviceId from list_booking_services) and format hint for date (YYYY-MM-DD).

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 the tool retrieves available time slots for a Wix Bookings service on a given date. Specifies the source of serviceId (list_booking_services), which distinguishes it from sibling tools like create_booking.

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?

Provides clear usage instructions: need serviceId, date in YYYY-MM-DD, and same place_slug. Warns about timezone behavior. Does not explicitly state when not to use or alternatives, but context is implied.

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

All Vila Madalena 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/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: search, get, list, create, submit, etc. Potential overlaps like create_booking vs request_reservation vs reserve_event_tickets are clarified by descriptions distinguishing appointment booking, restaurant table requests, and event ticket holds.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., list_services, get_place, create_booking). No mixing of styles, and verbs accurately describe the operation.

Tool Count4/5

28 tools is slightly above typical range but well-justified given the breadth of the site (places, events, movies, food, booking, forms, etc.). Each tool serves a clear purpose without feeling bloated.

Completeness4/5

Covers major read and action scenarios for a neighborhood directory. Missing update/delete operations for places and bookings, but those are likely not exposed via this API. Minor gaps like canceling reservations are handled externally.

Resources

Need Help?