MCP Near Me

List my appointments

list_my_service_bookings

Read-onlyIdempotent

Use immediately when the user asks to see or manage appointments. For cancellation or rescheduling, pass status='active'. Active means a confirmed or rescheduled appointment whose arrival window has not ended; past or terminal bookings are never active. If multiple active appointments are returned, show the choices instead of guessing. Connect is handled by the platform; never ask for a phone or code in chat.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`status`	No	Use 'active' for cancellation or rescheduling. It returns only actionable appointments whose arrival window has not ended; omit to include history.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

changedInput schema / properties / status / description

Previous value: -"Use 'active' for reschedule or cancellation requests; otherwise omit to include appointment history."New value: +"Use 'active' for cancellation or rescheduling. It returns only actionable appointments whose arrival window has not ended; omit to include history."

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "active_count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      },
-      "bookings": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "arrival_window": {
-              "type": "string"
-            },
-            "booking_id": {
-              "type": "string"
-            },
-            "provider_public_name": {
-              "type": "string"
-            },
-            "public_booking_ref": {
-              "type": "string"
-            },
-            "service_date": {
-              "type": "string"
-            },
-            "status": {
-              "type": "string"
-            },
-            "timezone": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "booking_id",
-            "provider_public_name",
-            "service_date",
-            "arrival_window",
-            "timezone",
-            "status",
-            "public_booking_ref"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "count": {
-        "maximum": 9007199254740991,
-        "minimum": -9007199254740991,
-        "type": "integer"
-      }
-    },
-    "required": [
-      "bookings",
-      "count",
-      "active_count"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "category": {
-            "type": "string"
-          },
-          "code": {
-            "type": "string"
-          },
-          "correlation_id": {
-            "type": "string"
-          },
-          "details": {
-            "additionalProperties": {},
-            "propertyNames": {
-              "type": "string"
-            },
-            "type": "object"
-          },
-          "message": {
-            "type": "string"
-          },
-          "retryable": {
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "code",
-          "category",
-          "message",
-          "retryable",
-          "correlation_id",
-          "details"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "error"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "active_count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      },
+      "bookings": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "arrival_window": {
+              "type": "string"
+            },
+            "booking_id": {
+              "type": "string"
+            },
+            "is_active": {
+              "type": "boolean"
+            },
+            "is_manageable": {
+              "type": "boolean"
+            },
+            "is_past": {
+              "type": "boolean"
+            },
+            "provider_public_name": {
+              "type": "string"
+            },
+            "public_booking_ref": {
+              "type": "string"
+            },
+            "service_date": {
+              "type": "string"
+            },
+            "status": {
+              "type": "string"
+            },
+            "timezone": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "booking_id",
+            "provider_public_name",
+            "service_date",
+            "arrival_window",
+            "timezone",
+            "status",
+            "public_booking_ref",
+            "is_active",
+            "is_manageable",
+            "is_past"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "count": {
+        "maximum": 9007199254740991,
+        "minimum": -9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "bookings",
+      "count",
+      "active_count"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "correlation_id": {
+            "type": "string"
+          },
+          "details": {
+            "additionalProperties": {},
+            "propertyNames": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "message": {
+            "type": "string"
+          },
+          "retryable": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "code",
+          "category",
+          "message",
+          "retryable",
+          "correlation_id",
+          "details"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  }
+]

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds substantial behavioral context: it precisely defines 'active' as a confirmed or rescheduled appointment whose arrival window has not ended, states that past/terminal bookings are never active, instructs the agent to present choices rather than guess, and warns not to ask for phone/code because Connect is handled by the platform. This materially shapes both tool invocation and conversation behavior.

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?

The description is four short, purposeful sentences, front-loaded with the immediate-use directive. Each sentence earns its place: when to use, status semantics, multi-result handling, and platform/communication guardrails. There is no filler or repetition of the annotation flags.

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?

The tool is a read-only listing operation with two optional parameters and an output schema, and the description covers the key semantic nuance (active status), multi-result behavior, and user-communication constraints. It does not mention limit/pagination behavior or explicitly contrast with the singular get_my_service_booking, but these are relatively low-stakes given the output schema and the rest of the context. Overall, sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The status parameter is already documented in the schema with essentially the same wording as the description, so the description adds only minor clarification ('past or terminal bookings are never active'). The 'limit' parameter receives no semantic explanation in either the schema or the description, and the description does not compensate for that gap. With 50% schema description coverage, the description is adequate but not additive beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: 'list my service bookings' / 'List my appointments' and says to use it 'immediately when the user asks to see or manage appointments.' However, it does not explicitly distinguish this listing tool from the sibling 'get_my_service_booking' (singular), so sibling differentiation is implicit rather than explicit.

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 description gives strong context for when to use the tool: use it for seeing/managing appointments, pass status='active' for cancellation or rescheduling, and show choices instead of guessing when multiple active appointments are returned. It does not state when not to use the tool or name alternatives, so it lacks explicit exclusions.

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

All MCP Near Me 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?