Skip to main content
Glama

Yoya Booking

by io.github.makloai
OverviewDiscussionsAdmin

Find available meeting times

list_available_times
Read-onlyIdempotent

Find up to 10 times (max 50), labeled in the guest's IANA timezone. Filter by inclusive from/exclusive to datetimes and morning (06–12), afternoon (12–18) or evening (18–24) in the guest timezone. Pass nextCursor unchanged to continue with the same filters. Slots are suggestions; preview then book rechecks availability. Never invent slot IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo
fromNo
slugYes
limitNo
cursorNo
timezoneNo
timeOfDayNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
codeNo
messageNo
nextCursorNo
nextOffsetNo
syncStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / cursor
      Added value: +{
+  "pattern": "^s_\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}Z$",
+  "type": "string"
+}
    • addedInput schema / properties / from
      Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 10,
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / slug / maxLength
      Added value: +2048
    • addedInput schema / properties / timeOfDay
      Added value: +{
+  "enum": [
+    "morning",
+    "afternoon",
+    "evening"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / timezone
      Added value: +{
+  "maxLength": 100,
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "nextCursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nextOffset": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "syncStatus": {
+      "enum": [
+        "pending",
+        "ready",
+        "attention"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, so safety is covered. The description adds real behavioral context beyond that: the 50-slot cap, cursor continuation semantics ('same filters'), the caveat that slots are advisory, and the explicit 'Never invent slot IDs' guardrail.

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?

Four dense sentences, front-loaded with the core action and constraints, with no filler. Each sentence carries a distinct constraint (cap, filters, pagination, correctness guardrail).

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?

For a paginated, timezone-sensitive query tool with 7 params, 0% schema coverage and an existing output schema, the description covers nearly everything an agent needs to call it correctly. The only gap is the undocumented slug param and the cursor/nextCursor naming inconsistency.

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 description coverage is 0%, so the description carries the burden and mostly delivers: it explains limit bounds (10/max 50), inclusive from / exclusive to, the morning/afternoon/evening split with hour ranges, and timezone labeling. It leaves slug unexplained and names the cursor parameter 'nextCursor' while the schema calls it 'cursor', a minor mismatch.

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 ('Find up to 10 times') with concrete scope and output characteristics. An agent can distinguish this listing/queries tool from the booking siblings (preview_booking, book_meeting) without opening the schema.

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?

The line 'Slots are suggestions; preview then book rechecks availability' implicitly routes the agent to preview_booking then book_meeting after listing. Clear usage context, but it does not explicitly name those alternatives or state when-not to use this tool.

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

All Yoya Booking toolsInspect
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