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. `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.
`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.

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.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 meaningful behaviors: no authentication required, PII-minimal output, Pacific-time fields, and a not-found error for bad references. This gives an agent realistic expectations for invocation and response handling.

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 is compact and front-loaded with the core purpose, followed by when to use it, the parameter, output characteristics, and error behavior. Every sentence earns its place and no filler is present.

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?

With one required parameter, full schema coverage, an output schema, and safety annotations already present, the description adds the remaining context an agent needs: authentication requirements, PII boundaries, time zone, and failure mode. Nothing important appears 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 schema's property description already explains that `reference` accepts the submission id or the emailed token. The description essentially restates this, adding no new semantic information beyond what the schema provides, so the baseline 3 applies.

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 what became of a previously submitted request.' It also distinguishes from sibling tools by enumerating the status transitions it covers (confirmed, moved, cancelled, merged), making its role as a read-only status lookup unmistakable.

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 explicitly states when to use the tool: 'Use when the customer asks whether the notary confirmed, moved, cancelled, or merged it.' It also notes that no sign-in is needed, but it does not name sibling alternatives or explicitly describe when not to use it, so it stops short of a full when/when-not guide.

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?