Skip to main content
Glama

Agenda SP

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

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

With no annotations, the description must disclose behaviors. It reveals that slot times are in the venue's timezone, which is critical for correct interpretation. No mention of idempotency or error handling, but for a read tool this is sufficient.

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?

Three sentences with no filler. Purpose is front-loaded in the first sentence. Every sentence provides essential information.

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 no output schema, the description explains output is 'available time slots' and adds timezone nuance. Could specify slot structure (e.g., start/end), but overall adequate for a 3-parameter tool.

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?

All three parameters have schema descriptions (100% coverage). The description adds value by reinforcing the need to reuse place_slug from list_booking_services and clarifying date format. This enriches the 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?

The description clearly states the verb ('Get'), resource ('available time slots'), and context ('Wix Bookings'). It also references a sibling tool (list_booking_services) to show data provenance, making the purpose distinct.

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 tells the agent to pass serviceId from list_booking_services, date in YYYY-MM-DD, and the same place_slug. Provides a behavioral caveat about timezone. Lacks explicit guidance on when NOT to use, but otherwise strong.

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

All Agenda SP 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
Disambiguation4/5

Tools are mostly distinct with clear descriptions. Some overlap in actions that require user to click a link (create_booking, create_checkout, request_reservation, etc.), but each targets a different domain (booking, store, restaurant, event tickets, RSVP). Minor ambiguity possible but descriptions clarify.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., create_booking, get_availability, search_places). No deviations or mixed conventions.

Tool Count4/5

28 tools is slightly high for a neighborhood directory, but each serves a specific function (search, booking, events, movies, offers, etc.). The scope justifies the count, though some tools like list_blog_posts and list_faqs might be considered niche.

Completeness4/5

The tool set covers search, place details, categories, menus, events, movies, offers, booking, and forms. Missing update/delete operations for places or user management, but these are likely out of scope for a read-only directory. Core queries and actions are well-supported.

Resources