Andrii Co. Notary & Apostille Assistant

check_service_area

Read-only

Check whether an address sits inside our Washington coverage and resolves precisely enough to book. Use when the customer wants an area answer without searching slots — search_availability already validates the area itself. Accepts: address (e.g. a Seattle street or ZIP) and optional service — notary or apostille rules differ. Returns withinServiceArea, distanceMiles, precise; if the address cannot be resolved the message says not found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	Street address, city, or ZIP to check (Washington State service area).
`service`	No	"notary" (default) or "apostille" — the service-area rules differ slightly.

Output Schema

TableJSON Schema

Name	Required	Description
`label`	No	Formatted address, or null when the address could not be resolved.
`region`	No
`country`	No
`message`	No	Why the place is not bookable as given, or null.
`precise`	Yes	False when a street and city are still needed to pin the spot.
`distanceMiles`	No	Straight-line miles from the Bothell office (display only, not a routed leg).
`withinServiceArea`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedJul 21, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the read-only and non-destructive nature. The description goes beyond annotations by disclosing the return fields (withinServiceArea, distanceMiles, precise) and the failure behavior ('if the address cannot be resolved the message says not found'). It adds meaningful behavioral context, though it doesn't detail resolution thresholds or geocoding 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?

Three sentences with each one earning its place: purpose and scope, usage guidance with alternative, then parameter and return behavior. The information is front-loaded, and 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?

For a two-parameter read-only tool with an output schema and clear annotations, the description covers everything an agent needs: use case, parameter semantics, return values, and not-found handling. No critical information is missing.

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?

Input schema already covers both parameters with 100% description coverage, so the baseline is 3. The description adds extra value by giving an example of an acceptable address ('a Seattle street or ZIP') and explaining why service matters ('notary or apostille rules differ'), supplementing the schema with practical usage meaning.

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 a specific verb and resource: 'Check whether an address sits inside our Washington coverage and resolves precisely enough to book.' It also immediately differentiates itself from the sibling search_availability, so an agent knows exactly what this tool does and what it does not do.

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?

The description explicitly states when to use this tool: 'Use when the customer wants an area answer without searching slots' and names the alternative, search_availability, which 'already validates the area itself.' It also notes that the optional service parameter changes notary vs. apostille rules, giving the agent clear selection criteria.

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 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?