Andrii Co. Notary & Apostille Assistant

request_apostille

Submit a mail-in apostille request — a lead for already-certified Washington public records needing NO notarization (e.g. birth or marriage certificates). Use when get_apostille_requirements says they qualify. Requires: documents, name, and an email or phone; the notary replies with mailing instructions and a quote — nothing charged until approved. Pass existing_reference to extend an open request. Returns a reference; fails if the name or a valid contact is missing.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The customer's FULL LEGAL NAME exactly as on their government-issued ID (never a nickname) — apostille filings print it.
`email`	No	Email. Collect BOTH an email AND a phone in one question when possible; at least one is required.
`notes`	No	Anything else the notary should know.
`phone`	No	Phone with country code — the notary confirms fastest by phone/SMS.
`documents`	Yes	What documents, in plain words (e.g. "2 birth certificates for Ukraine").
`existing_reference`	No	To ADD these documents to an EXISTING request instead of creating a second one, pass that request's reference id (with the same email/phone so we can verify the customer). Nothing new is created.
`destination_country`	No	Destination country the apostilled documents are for.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`status`	No	Account tools: the booking's status after this call (Pending after book_appointment).
`message`	Yes	Customer-facing outcome; relay it as written — bookings are requests until the notary confirms.
`manageUrl`	No	Guest requests: the emailed confirm/cancel link, when one was minted (null otherwise).
`onAccount`	No	True when the request was filed on the signed-in customer's own account — they can then list it with my_bookings and change it with reschedule_booking / cancel_booking. Absent or false means a guest request, managed through the emailed link.
`reference`	No	Request / order reference for check_request_status (guest tools) or my_bookings (account tools).
`appendedToExisting`	No	True when existing_reference was given and the request was extended, not duplicated.
`ourComparableQuoteCents`	No	request_price_match only, when computable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "appendedToExisting": {
+      "description": "True when existing_reference was given and the request was extended, not duplicated.",
+      "type": "boolean"
+    },
+    "manageUrl": {
+      "description": "Guest requests: the emailed confirm/cancel link, when one was minted (null otherwise).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "Customer-facing outcome; relay it as written — bookings are requests until the notary confirms.",
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "onAccount": {
+      "description": "True when the request was filed on the signed-in customer's own account — they can then list it with my_bookings and change it with reschedule_booking / cancel_booking. Absent or false means a guest request, managed through the emailed link.",
+      "type": "boolean"
+    },
+    "ourComparableQuoteCents": {
+      "description": "request_price_match only, when computable.",
+      "type": "integer"
+    },
+    "reference": {
+      "description": "Request / order reference for check_request_status (guest tools) or my_bookings (account tools).",
+      "type": "string"
+    },
+    "status": {
+      "description": "Account tools: the booking's status after this call (Pending after book_appointment).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "message"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description discloses behaviors well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false): it reveals this creates a lead, not a confirmed order; that the notary asynchronously 'replies with mailing instructions and a quote'; that 'nothing charged until approved'; that existing_reference extends an open request; and that it 'fails if the name or a valid contact is missing.' This gives the agent a realistic model of the tool's side effects and non-deterministic human-in-the-loop behavior, which openWorldHint alone does not convey.

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?

Roughly four sentences contain the core purpose, the gating condition, required fields, the async reply flow, pricing behavior, extension semantics, and failure modes. The most important constraint (what this tool is for) is front-loaded, and every sentence adds non-redundant information. No filler 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?

For a 7-parameter, 2-required tool with a rich output schema, the description is complete: it covers eligibility, prerequisites, the asynchronous process, approval/payment semantics, the extension path, the return value ('Returns a reference'), and failure conditions. Nothing an agent needs to decide whether and how to call it is left unstated.

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 description coverage is 100%, so baseline is 3. The description adds only marginal parameter insight beyond the schema: it reinforces that 'an email or phone' is required (already stated in the email property's schema description) and ties failure to missing name/contact. It does not add format, syntax, or value details 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?

The description states a specific verb and resource: 'Submit a mail-in apostille request — a lead for already-certified Washington public records needing NO notarization.' The scope is sharply delimited (mail-in, certified records, no notarization), which clearly separates it from siblings like request_booking, request_price_match, and get_apostille_requirements. The eligibility boundary ('already-certified', 'NO notarization') makes the tool's identity unambiguous.

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 gives an explicit when-to-use condition tied to a named sibling: 'Use when get_apostille_requirements says they qualify.' The 'already-certified ... needing NO notarization' phrasing implicitly states when-not-to-use (records still needing notarization or certification), and the lead-based nature distinguishes it from booking/price-match siblings.

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?