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

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

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 changedOct 14, 2026

addedOutput schema / properties / destination / properties / effectiveDate / description

Added value: +"YYYY-MM-DD the Convention enters into force for a state that joined by a dated accession: still ahead for coming_soon, already past for a recent member."

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.2/5.0

Behavior4/5

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

Annotations already establish the safe read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds real behavioral context beyond them: unclear wording returns an 'unknown' category rather than erroring, and it previews what comes back (category, do-it-yourself path, offer).

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 the core question and the category rules in dense, information-bearing clauses with no filler. Slightly long as a single run-on paragraph, but every clause adds routing or behavior value.

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 an output schema present the description needn't detail return values, yet it still covers the trigger, the accepted inputs, the category outcomes, and the no-error fallback. Nothing an agent needs to call it correctly 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 description coverage is 100%, so the baseline is 3. The description restates the three accepted inputs ('document' in plain words, optional issuing_state, destination_country) without adding format or constraint detail the schema lacks.

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?

Specific verb+resource ('Check whether a document can get an apostille and how') with the routing logic spelled out (vital records mail as-is, private papers need notarization, federal ones go to State Dept). This cleanly separates it from the sibling request_apostille, which places the order rather than answering eligibility.

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 an explicit trigger: 'Use when the customer asks is this apostillable.' The alternative (request_apostille) is never named, so the agent must infer that this is the pre-check and not the order path.

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?