Andrii Co. Notary & Apostille Assistant

get_apostille_requirements

Read-only

Check whether a document can get an apostille and how: certified vital records mail in as-is, private papers (e.g. a diploma or POA) need notarization first, federal ones go to the US Department of State. Use when the customer asks is this apostillable. Accepts: document in plain words, optional issuing_state, destination_country. Returns the category, the honest do-it-yourself path and our offer; unclear wording yields an unknown category, never an error.

Input Schema

TableJSON Schema

Name	Required	Description
`document`	Yes	The document in plain words (e.g. "Washington birth certificate", "university diploma", "FBI background check", "power of attorney").
`issuing_state`	No	The US state that issued or notarized it (default Washington).
`destination_country`	No	The country the apostilled document is for.

Output Schema

TableJSON Schema

Name	Required	Description
`diyPath`	Yes
`category`	Yes	Document class: vital_record_mailin_ready, needs_notarized_copy, notarized_document, court_document, federal_authentication, unknown.
`document`	Yes
`ourOffer`	Yes
`disclaimer`	No
`destination`	No
`explanation`	Yes
`howToProceed`	No
`issuingState`	Yes
`eligibleForMailInAsIs`	Yes	True when no notarial act is needed first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "category": {
+      "description": "Document class: vital_record_mailin_ready, needs_notarized_copy, notarized_document, court_document, federal_authentication, unknown.",
+      "type": "string"
+    },
+    "destination": {
+      "properties": {
+        "country": {
+          "type": "string"
+        },
+        "effectiveDate": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "status": {
+          "description": "member | coming_soon | non_member.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "country",
+        "status"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "disclaimer": {
+      "type": "string"
+    },
+    "diyPath": {
+      "properties": {
+        "stateFee": {
+          "type": "string"
+        },
+        "whenToUseUs": {
+          "type": "string"
+        },
+        "yourself": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "document": {
+      "type": "string"
+    },
+    "eligibleForMailInAsIs": {
+      "description": "True when no notarial act is needed first.",
+      "type": "boolean"
+    },
+    "explanation": {
+      "type": "string"
+    },
+    "howToProceed": {
+      "type": "string"
+    },
+    "issuingState": {
+      "type": "string"
+    },
+    "ourOffer": {
+      "properties": {
+        "fullServiceTiers": {
+          "type": "string"
+        },
+        "inPersonApostilleFromCents": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "mailInApostilleFromCents": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "typicalTurnaround": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "typicalTurnaroundTier": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "document",
+    "issuingState",
+    "category",
+    "eligibleForMailInAsIs",
+    "explanation",
+    "diyPath",
+    "ourOffer"
+  ],
+  "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 readOnly and destructive annotations, the description discloses the three-path processing logic, the exact contents of the response (category, DIY path, offer), and the edge-case guarantee that unclear wording yields an 'unknown' category rather than an error. This is substantial 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.

Conciseness5/5

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

The description is a single dense paragraph that front-loads purpose, then covers categories, trigger, parameters, and behavior. Every clause carries distinct information, and there is no filler or repetition of schema content.

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 that an output schema is present, the description does not need to detail return fields. It fully covers input expectations, decision categories, the DIY path, and the fallback behavior, making it complete for an informational lookup tool.

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% with meaningful descriptions for all three parameters, so the baseline is 3. The description adds only that 'document' should be in plain words and that the other two are optional, which is minor and mostly redundant with the schema's default null values.

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: 'Check whether a document can get an apostille and how,' and immediately distinguishes the three document categories (vital records, private papers, federal). This makes it clear what the tool does and separates it from action-oriented siblings like request_apostille.

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 names the trigger condition: 'Use when the customer asks is this apostillable,' which is clear and precise. It does not explicitly name when not to use this tool or call out alternatives, but the trigger is specific enough that an agent can route correctly against sibling tools.

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?