MONO Social

get_availability

Read-onlyIdempotent

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serviceId": "<serviceId>",
      "date": "<date>"
    },
    "name": "get_availability"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format.
`serviceId`	Yes	Service ID from list_booking_services.
`place_slug`	No	Venue place slug — use the same one passed to list_booking_services.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format (e.g. \"2026-06-25\")."New value: +"Date in YYYY-MM-DD format."

addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-06-25"
+]
```

First observedJul 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so safety is covered. The description adds a genuinely useful trait beyond that: slot times are returned in the VENUE's timezone, which is not necessarily the directory's — a non-obvious behavior an agent would likely get wrong.

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 short sentences, front-loaded with the purpose, then prerequisites, then the timezone caveat. No filler sentences and nothing redundant with structured fields.

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?

With no output schema, the description carries return-value burden and does address the key return detail (slot times plus their timezone). It does not describe the shape of the slot list or behavior when no slots exist, which is a minor gap for an otherwise complete definition.

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 the baseline is 3, but the description adds real meaning: it names the source of serviceId (list_booking_services) and explains that place_slug must match the earlier call because it governs the returned timezone. That links a parameter to an observable output behavior rather than just restating 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?

States a specific verb and resource — 'Get available time slots for a bookable service on a given date' — and scopes it to Wix Bookings. This clearly separates it from list_booking_services, get_event_tickets, and the booking-creation siblings.

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 routes the agent to call list_booking_services first and reuse its serviceId and place_slug, which conveys the intended call sequence. It stops short of stating exclusions (e.g. what to do for multi-day ranges or unavailable dates), so it's clear but not fully exhaustive.

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

All MONO Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?