Skip to main content
Glama

Centro

by io.github.junoventures

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
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format (e.g. "2026-06-25").
serviceIdYesService ID from list_booking_services.
place_slugNoVenue place slug — use the same one passed to list_booking_services.

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided; description takes full burden. Explicitly discloses timezone behavior (venue timezone, not directory's). Lack of annotations means no contradiction. Adequate for a read tool, but could mention idempotency or permissions.

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. Every sentence adds value. No extraneous text.

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?

No output schema, but description clarifies that slot times are returned. Could briefly describe response structure (e.g., start/end times), but sufficient for agent to infer.

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 critical context not in schema: ties serviceId to list_booking_services, reinforces date format, and emphasizes place_slug must match previous call. Provides integration guidance beyond schema.

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?

Description states 'Get available time slots for a bookable service on a given date (Wix Bookings)' - specific verb, resource, and context. Distinct 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 explicit parameter instructions: use serviceId from list_booking_services, date in YYYY-MM-DD, and same place_slug. Notes timezone behavior. Could mention when not to use, but context implies usage for pre-booking check.

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

All Centro 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.2/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose. Tools like create_booking and request_reservation target different services (appointments vs. restaurant tables), and reserve_event_tickets vs. rsvp_event differentiate paid holds from free RSVPs. No overlapping functionality that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_dishes) using lowercase with underscores. No mixing of conventions or irregular verbs.

Tool Count4/5

28 tools cover a broad domain of neighborhood directory services (bookings, events, movies, restaurant menus, forms, etc.). While the count is slightly high, each tool serves a specific function and is justified by the domain scope.

Completeness5/5

The tool set provides comprehensive coverage for a neighborhood directory: search, booking, reservations, event management, menus, reviews, forms, loyalty, and more. No obvious gaps; all core user needs are addressed.

Resources