MCC Solutions

How to get an apostille

apostille_route

Read-onlyIdempotent

For a U.S. state (and optionally the destination country), return which office issues the apostille, its fee and options, whether a county clerk step comes first, whether the country accepts apostilles, and where to order the work from MCC Solutions.

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": {
      "state": "<state>"
    },
    "name": "apostille_route"
  }
}

Input Schema

Name	Required	Description	Default
`state`	Yes	Two-letter state code or state name that issued or notarized the document, e.g. NY
`country`	No	Destination country, e.g. Spain (optional)

Output Schema

Name	Required	Description	Default
`fee`	Yes
`state`	Yes
`office`	No
`options`	Yes
`sources`	No
`disclaimer`	No
`processing`	Yes
`destination`	No
`state_guide`	No
`order_from_mcc`	No
`county_step_first`	No
`federal_documents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context by enumerating what the response covers (issuing office, fee, county clerk prerequisite, country acceptance, ordering path). It does not say whether fee data can be stale or what happens for an unrecognized state, which keeps it at a 3.

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?

One front-loaded sentence that scopes the input first and then lists the outputs. It is dense and every clause carries information, though the single run-on structure and the trailing MCC Solutions upsell make it slightly heavier than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so the description does not need to document return shape or side effects. What it provides — scope, inputs, and the categories of information returned — is sufficient for correct invocation; only edge-case behavior (invalid state, stale fees) is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining that 'country' is optional and what it is used for — determining whether the destination accepts apostilles — which the schema's bare 'Destination country, e.g. Spain' does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb+resource: 'For a U.S. state ... return which office issues the apostille, its fee and options, whether a county clerk step comes first...'. That is far more specific than the title and lets an agent distinguish it from lookup-style siblings such as get_services_and_prices. It stops short of naming any sibling, so it does not fully meet the 'distinguishes from siblings' bar for a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the input ('For a U.S. state ... optionally the destination country') but there is no explicit when-to-use statement, no when-not, and no pointer to an alternative tool for related questions like notarization. An agent can infer the context but must guess at the boundaries.

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

All MCC Solutions 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?