MCP Near Me

Open secure appointment management

open_service_account

Read-onlyIdempotent

Use only when the user explicitly asks to view, reschedule or cancel existing appointments or manage saved addresses. Opens the existing first-party account portal inside a card, never returns customer data. Never call for general questions or new bookings. The customer signs in and makes changes inside the card on MCP Near Me; never ask to connect or reconnect a ChatGPT account, and never request a phone or code in chat. When a live card is displayed, omit prose or use at most one short neutral sentence: use only assistant_message in the customer's language (English: "Details and current status are in the card."). End the reply there. Do not add an introduction, summary, instructions to review or confirm, or claims that a booking is created or not yet created: this text remains after the card changes. Do not repeat companies, dates, times, prices, policies, booking references, status claims, comparisons or next steps outside the card. This applies only to successful card presentation; keep normal intake/choice questions and concise error or unavailable-UI guidance.

Input Schema

Name	Required	Description	Default
`intent`	No		view

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "account_url": {
-        "type": "string"
-      },
-      "authentication": {
-        "const": "first_party_only",
-        "type": "string"
-      },
-      "intent": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "account_url",
-      "intent",
-      "authentication"
-    ],
-    "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": {
+      "account_url": {
+        "type": "string"
+      },
+      "assistant_message": {
+        "const": "Details and current status are in the card.",
+        "description": "The only permitted optional caption for the live card. Translate to the customer's language without adding details or instructions.",
+        "type": "string"
+      },
+      "authentication": {
+        "const": "first_party_only",
+        "type": "string"
+      },
+      "intent": {
+        "type": "string"
+      },
+      "presentation": {
+        "const": "interactive_card",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_url",
+      "intent",
+      "authentication",
+      "presentation",
+      "assistant_message"
+    ],
+    "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"
+  }
+]

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Although annotations already mark this as read-only, idempotent, and non-destructive, the description adds substantial behavioral context: no customer data is returned, the customer signs in inside the card, and account credentials should not be requested in chat. It also describes how to handle the assistant message after successful card presentation and what text must not remain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the key usage rule, but it is extremely long and repetitive around response formatting and card presentation constraints. Much of the guidance is useful, but several sentences restate the same point, making it less concise than ideal.

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 the rich annotations and the presence of an output schema, the description covers the important behavioral details: when to call, what happens inside the card, data privacy, and how to phrase the assistant message. The only notable gap is explicit parameter semantics for `intent`, but the overall agent guidance is otherwise complete.

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 schema has 0% description coverage for the single `intent` parameter, so the description must carry that burden. It implies the available actions (view, reschedule, cancel) but does not explicitly document the `intent` parameter, its enum values, or the default value of `view`, leaving the schema to define those mechanics.

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 gives a specific verb and resource: it opens the existing first-party account portal inside a card for viewing, rescheduling, or canceling appointments and managing addresses. It clearly distinguishes this from sibling tools by stating it is for existing appointments, not new bookings or general service questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is explicitly constrained: call only when the user explicitly asks to view, reschedule, cancel, or manage saved addresses, and never for general questions or new bookings. The description also explains the authentication flow and when not to ask for account reconnection or chat-based codes.

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?