Skip to main content
Glama

Book ShesMyDogLady

by com.enhancedint
OverviewDiscussionsAdmin

Find open times

find_times
Read-onlyIdempotent

Find the start times that are open for one visit (a service from the card whose bookable is true), between two dates (at most 14 days). Each time's end includes the minutes the business takes to settle the dog in. Pass windows (the customer's free time from their calendar) to get only the starts that fit both calendars. Returns ISO 8601 times with offsets. Only open times are ever shown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesLast day, YYYY-MM-DD. At most 14 days from `from`, counting both, and at most 60 days from today.
fromYesFirst day, YYYY-MM-DD, in the business's time zone (the card names it). Not in the past.
itemsYesExactly one visit. Each visit is booked on its own; add-ons the service takes go in answers.addons.
windowsNoThe customer's free time, as intervals with offsets. When given, only starts whose whole visit (its length plus its settling time) fits inside one window come back. Leave out to see every open start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-16",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-22",
-    "windows": [
-      {
-        "end": "2026-10-16T17:00:00-07:00",
-        "start": "2026-10-16T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-17",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-23",
+    "windows": [
+      {
+        "end": "2026-10-17T17:00:00-07:00",
+        "start": "2026-10-17T09:00:00-07:00"
+      }
+    ]
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-15",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-21",
-    "windows": [
-      {
-        "end": "2026-10-15T17:00:00-07:00",
-        "start": "2026-10-15T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-16",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-22",
+    "windows": [
+      {
+        "end": "2026-10-16T17:00:00-07:00",
+        "start": "2026-10-16T09:00:00-07:00"
+      }
+    ]
+  }
+]
  3. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-14",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-20",
-    "windows": [
-      {
-        "end": "2026-10-14T17:00:00-07:00",
-        "start": "2026-10-14T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-15",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-21",
+    "windows": [
+      {
+        "end": "2026-10-15T17:00:00-07:00",
+        "start": "2026-10-15T09:00:00-07:00"
+      }
+    ]
+  }
+]
  4. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-13",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-19",
-    "windows": [
-      {
-        "end": "2026-10-13T17:00:00-07:00",
-        "start": "2026-10-13T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-14",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-20",
+    "windows": [
+      {
+        "end": "2026-10-14T17:00:00-07:00",
+        "start": "2026-10-14T09:00:00-07:00"
+      }
+    ]
+  }
+]
  5. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-12",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-18",
-    "windows": [
-      {
-        "end": "2026-10-12T17:00:00-07:00",
-        "start": "2026-10-12T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-13",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-19",
+    "windows": [
+      {
+        "end": "2026-10-13T17:00:00-07:00",
+        "start": "2026-10-13T09:00:00-07:00"
+      }
+    ]
+  }
+]
  6. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-11",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-17",
-    "windows": [
-      {
-        "end": "2026-10-11T17:00:00-07:00",
-        "start": "2026-10-11T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-12",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-18",
+    "windows": [
+      {
+        "end": "2026-10-12T17:00:00-07:00",
+        "start": "2026-10-12T09:00:00-07:00"
+      }
+    ]
+  }
+]
  7. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-10",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-16",
-    "windows": [
-      {
-        "end": "2026-10-10T17:00:00-07:00",
-        "start": "2026-10-10T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-11",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-17",
+    "windows": [
+      {
+        "end": "2026-10-11T17:00:00-07:00",
+        "start": "2026-10-11T09:00:00-07:00"
+      }
+    ]
+  }
+]
  8. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "from": "2026-10-09",
-    "items": [
-      {
-        "slug": "meet-greet"
-      }
-    ],
-    "to": "2026-10-15",
-    "windows": [
-      {
-        "end": "2026-10-09T17:00:00-07:00",
-        "start": "2026-10-09T09:00:00-07:00"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "from": "2026-10-10",
+    "items": [
+      {
+        "slug": "meet-greet"
+      }
+    ],
+    "to": "2026-10-16",
+    "windows": [
+      {
+        "end": "2026-10-10T17:00:00-07:00",
+        "start": "2026-10-10T09:00:00-07:00"
+      }
+    ]
+  }
+]
  9. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value beyond them by disclosing that a returned time's end already includes the business's settling minutes and that only open times are ever surfaced. It omits nothing critical, though it doesn't cover error behavior or timezone-conflict handling.

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 front-loaded sentences, each carrying a distinct fact (what is returned, the settle-time inclusion, the windows narrowing, the return format). No padding or restatement of the title.

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

Completeness5/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 takes on the burden of describing return values and does so ('ISO 8601 times with offsets', only open ones). Combined with a thorough schema and annotations covering safety, an agent has everything needed to call this correctly.

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, and the description earns an increment by re-framing `windows` as 'the customer's free time from their calendar' and stating the both-calendars fitting rule in plain terms. It does not add format detail for `items`, `from`, or `to` beyond what the schema already documents.

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 the start times that are open') and constrains the scope to exactly one visit from a service whose bookable flag is true. An agent can immediately separate this availability-lookup from the write-oriented siblings book/cancel_booking without opening a 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?

Explains the key conditional: pass `windows` (the customer's calendar) to get only starts fitting both calendars; omit it to see every open start. It does not name sibling tools or say explicitly to call this before `book`, so routing guidance is clear but not exhaustive.

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

All Book ShesMyDogLady 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