Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document": "<document>"
    },
    "name": "get_apostille_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesThe document in plain words (e.g. "Washington birth certificate", "university diploma", "FBI background check", "power of attorney").
issuing_stateNoThe US state that issued or notarized it (default Washington).
destination_countryNoThe country the apostilled document is for.

Output Schema

NameRequiredDescriptionDefault
diyPathYes
categoryYesDocument class: vital_record_mailin_ready, school_record, notarized_document, court_document, federal_authentication, unknown.
documentYes
ourOfferYes
disclaimerNo
destinationNo
explanationYes
howToProceedNo
issuingStateYes
eligibleForMailInAsIsYesTrue when no notarial act is needed first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / category / description
      Previous value: -"Document class: vital_record_mailin_ready, needs_notarized_copy, notarized_document, court_document, federal_authentication, unknown."New value: +"Document class: vital_record_mailin_ready, school_record, notarized_document, court_document, federal_authentication, unknown."
  2. Changed1 schema field changed
    • 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."
  3. Changed1 schema field changed
    • 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"
      +}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavior — unclear wording degrades to an 'unknown' category instead of raising an error, which tells the agent it can pass messy customer phrasing safely. It also previews the response shape (category, DIY path, offer), though that overlaps the output schema.

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?

The apostille decision rule is front-loaded and every sentence carries information: category rules, usage trigger, inputs, and failure mode. It is dense and slightly run-on, but no sentence is filler.

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 read-only three-parameter lookup with a full output schema and complete parameter descriptions, nothing an agent needs is missing: the domain rules, the trigger, acceptable input style, and the unknown-category fallback are all stated.

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 all three parameters are already documented, including the default of Washington for issuing_state and examples for document. The description's 'Accepts: document in plain words, optional issuing_state, destination_country' mostly restates the schema, adding only the note that free-text phrasing is acceptable — a baseline 3.

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 and resource ('Check whether a document can get an apostille and how') and immediately enumerates the three document categories with their distinct paths. This clearly separates it from sibling tools like request_apostille or get_price_quote, which act on a decision rather than informing it.

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'), which is a clear entry condition. It stops short of naming the alternative or the handoff (e.g. 'once confirmed, use request_apostille to order'), so the when-not side is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources