Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

by net.andrii
OverviewDiscussionsAdmin

search_availability

Read-only

Find open appointment slots (validating the meeting area too). Use when the customer wants a time. Requires: service (office, mobile, apostille); mobile needs an address, e.g. a Bothell street. Returns resolved location, up to 7 recommended slots with startUnix, and per-day windows — the k-th start is startUnixFrom + k*stepSec for k < startCount; hand the picked startUnix to request_booking as desired_time_unix. An ungeocodable address is flagged not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNoThe address to meet at — required for "mobile"; ignored for "office".
serviceYes"office" (at our office), "mobile" (we come to you), or "apostille".
document_countNoNumber of documents (drives the appointment length). Default 1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
resolvedYes
recommendedYes
afterHoursSurchargeCentsNoMobile services only: the surcharge an afterHours slot adds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Open slots over the booking horizon (Pacific time). `recommended` is what to offer; `days[].windows` encodes every bookable start losslessly: the k-th start is startUnixFrom + k*stepSec for k < startCount.",
+  "properties": {
+    "afterHoursSurchargeCents": {
+      "description": "Mobile services only: the surcharge an afterHours slot adds.",
+      "type": "integer"
+    },
+    "days": {
+      "items": {
+        "properties": {
+          "closed": {
+            "description": "Present only on a day with no bookable slot: closed | full.",
+            "type": "string"
+          },
+          "date": {
+            "description": "YYYY-MM-DD, Pacific.",
+            "type": "string"
+          },
+          "windows": {
+            "items": {
+              "properties": {
+                "afterHours": {
+                  "type": "boolean"
+                },
+                "fit": {
+                  "description": "great | good | fair | far.",
+                  "type": "string"
+                },
+                "from": {
+                  "description": "HH:MM of the first start.",
+                  "type": "string"
+                },
+                "startCount": {
+                  "type": "integer"
+                },
+                "startUnixFrom": {
+                  "type": "integer"
+                },
+                "stepSec": {
+                  "type": "integer"
+                },
+                "until": {
+                  "description": "HH:MM end of the last slot.",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "from",
+                "until",
+                "fit",
+                "startUnixFrom",
+                "startCount",
+                "stepSec"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "date",
+          "windows"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "recommended": {
+      "items": {
+        "properties": {
+          "date": {
+            "type": "string"
+          },
+          "durationMin": {
+            "type": "integer"
+          },
+          "fit": {
+            "description": "great | good | fair | far.",
+            "type": "string"
+          },
+          "start": {
+            "description": "HH:MM Pacific.",
+            "type": "string"
+          },
+          "startUnix": {
+            "description": "Pass to request_booking as desired_time_unix (or to book_appointment as scheduled_at).",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "date",
+          "start",
+          "startUnix",
+          "durationMin",
+          "fit"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "resolved": {
+      "properties": {
+        "country": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "distanceMiles": {
+          "description": "Straight-line miles from the Bothell office (display only, not a routed leg).",
+          "type": "number"
+        },
+        "label": {
+          "description": "Formatted address, or null when the address could not be resolved.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "message": {
+          "description": "Why the place is not bookable as given, or null.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "precise": {
+          "description": "False when a street and city are still needed to pin the spot.",
+          "type": "boolean"
+        },
+        "region": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "withinServiceArea": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "withinServiceArea",
+        "precise"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "resolved",
+    "days",
+    "recommended"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses concrete behavior: meeting-area validation, resolved location, up to 7 slot recommendations, per-day windows, the exact start-time formula, and the ungeocodable-address error case. This gives the agent a strong behavioral model.

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 front-loads the purpose, then packs only high-value usage, return, and error behavior into a compact paragraph. Every clause adds information; there is no filler or repetition of the schema.

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?

Given the output schema exists and the parameter schema is fully documented, the description covers the remaining operational details an agent needs: when to call it, how service/address interact, what the response contains, how to pass the result onward, and how errors surface.

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?

Schema coverage is 100%, so the schema already documents service, address, and document_count fully. The description adds a helpful example address and states the relationship between service and address, but these largely restate what the schema already says, so it does not significantly raise the baseline.

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 opens with the exact action and resource: finding open appointment slots, plus the additional validation of the meeting area. This clearly separates it from related tools like request_booking or check_service_area.

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?

It gives an explicit trigger ("Use when the customer wants a time") and explains the required service and address dependency for mobile appointments. It also directs the picked startUnix to request_booking, but it does not list explicit when-not cases or compare alternatives.

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

All Andrii Co. Notary & Apostille Assistant 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