Andrii Co. Notary & Apostille Assistant

check_request_status

Read-only

Check what became of a previously submitted request — no sign-in needed, guests welcome. Use when the customer asks whether the notary confirmed, moved, cancelled, or merged it. Accepts: reference — the id returned at submission or the token from the emailed confirm link. Returns the service plus status and timing (PII-minimal — never address, name, or notes; Pacific time, e.g. scheduledAtPacific). Fails if the reference is wrong — a not found reply.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`reference`	Yes	The reference id returned when the request was submitted (also accepts the token from the emailed confirm link).

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes
`status`	Yes	Pending \| Scheduled \| EnRoute \| InProgress \| Completed \| Notarized \| PickedUp \| Cancelled \| NoShow \| MergedWithOther. The STORED operator lifecycle — `Completed` means the notarial act happened (signed), not that the order is done. `note` says what the word means for the customer; read that rather than branching on this.
`service`	Yes	office \| apostille \| mobile \| loan \| ron \| apostille_mail; null on a legacy row.
`reference`	Yes
`mergedInto`	No	Only for MergedWithOther: the surviving appointment's status and time.
`scheduledAt`	No	Unix seconds.
`displayStatus`	No	The customer-facing word: {code, tone}. Code is the derived display status (Signed \| Apostilled \| ReadyToShip \| Shipped \| Complete \| PartiallyComplete \| DealDone \| …); tone is ok \| warn \| err \| info \| neutral. Quote the code's meaning from `note`, never the stored status.
`requestedTime`	No	Unix seconds the customer asked for on a lead, or null.
`scheduledAtPacific`	No
`awaitingCustomerConfirmation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / displayStatus

Added value: +{
+  "description": "The customer-facing word: {code, tone}. Code is the derived display status (Signed | Apostilled | ReadyToShip | Shipped | Complete | PartiallyComplete | DealDone | …); tone is ok | warn | err | info | neutral. Quote the code's meaning from `note`, never the stored status.",
+  "type": "object"
+}

changedOutput schema / properties / status / description

Previous value: -"Pending | Scheduled | EnRoute | InProgress | Completed | Notarized | PickedUp | Cancelled | NoShow | MergedWithOther. `note` says what the word means for the customer; read that rather than branching on this."New value: +"Pending | Scheduled | EnRoute | InProgress | Completed | Notarized | PickedUp | Cancelled | NoShow | MergedWithOther. The STORED operator lifecycle — `Completed` means the notarial act happened (signed), not that the order is done. `note` says what the word means for the customer; read that rather than branching on this."

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "PII-minimal status of a request — never the address, name or notes.",
+  "properties": {
+    "awaitingCustomerConfirmation": {
+      "type": "boolean"
+    },
+    "mergedInto": {
+      "description": "Only for MergedWithOther: the surviving appointment's status and time.",
+      "properties": {
+        "scheduledAt": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "scheduledAtPacific": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "reference": {
+      "type": "string"
+    },
+    "requestedTime": {
+      "description": "Unix seconds the customer asked for on a lead, or null.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "scheduledAt": {
+      "description": "Unix seconds.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "scheduledAtPacific": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "service": {
+      "description": "office | apostille | mobile | loan | ron | apostille_mail; null on a legacy row.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Pending | Scheduled | EnRoute | InProgress | Completed | Notarized | PickedUp | Cancelled | NoShow | MergedWithOther. `note` says what the word means for the customer; read that rather than branching on this.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "service",
+    "status",
+    "awaitingCustomerConfirmation",
+    "note"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations: discloses the auth profile (no sign-in), the privacy posture of the response (PII-minimal, never address/name/notes), timezone convention (Pacific, e.g. scheduledAtPacific), and the failure mode (not-found on a bad reference). This is rich, actionable behavioral context.

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

Conciseness4/5

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

Front-loads purpose, then usage, then parameter and return/failure notes in a tight paragraph with no filler. Slightly dense with parenthetical asides, but every clause earns its place.

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 one-parameter read tool with an output schema, the description supplies everything else an agent needs: eligibility, trigger conditions, input variants, privacy constraints, timezone, and error behavior. Nothing material is missing.

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% and the sole `reference` parameter is already documented in the schema. The description restates that it accepts the submission id or the emailed confirm-link token, adding little beyond what the schema says. Baseline 3 is correct when the schema carries the parameter definition.

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?

States a specific verb+resource ('check what became of a previously submitted request') and immediately scopes it apart from siblings by noting it needs no sign-in while other booking tools (my_bookings) do. An agent can tell what it does and who it serves without opening the schema.

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?

Gives a concrete trigger ('use when the customer asks whether the notary confirmed, moved, cancelled, or merged it') and an access condition (guests welcome, no sign-in). It does not explicitly name a when-not or a sibling alternative, so it stops short of 5.

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?