Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

get_turnaround_estimate

Read-only

Calculate typical turnaround — apostille processing days plus mailing and delivery legs. Ranges, never guarantees; exact appointment times come from search_availability. Use when the customer asks how long. Accepts: service (e.g. notarization, apostille, apostille_mail, loan_signing), optional tier, shipping, destination_country, ua_lane (withinUkraine | fromUsa — the Ukraine lane when shipping is omitted). Returns staged day estimates; an unknown tier falls back to the standard figure, not 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": {
      "service": "<service>"
    },
    "name": "get_turnaround_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoApostille speed tier when service is apostille: expedited | priority | standard.
serviceYesService: notarization | apostille | apostille_mail | loan_signing.
ua_laneNoUkraine delivery lane: withinUkraine (weekly batch) or fromUsa (direct from the USA) — each answers its `np_eta` window for a recipient whose postal code we do not know. Fills `shipping` when that is omitted; an explicit `shipping` always wins.
shippingNoDelivery: pickup | us | ukraine | ukraine_direct | international. If omitted, inferred from destination_country (apostille legs default to US shipping) or from `ua_lane` (fromUsa ⇒ ukraine_direct).
destination_countryNoDestination country (used to infer shipping when `shipping` is omitted).

Output Schema

NameRequiredDescriptionDefault
tierNo
stagesYes
serviceYes
disclaimerYes
howToProceedNo
typicalTotalDaysLowYes
typicalTotalDaysHighYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ua_lane / description
      Previous value: -"Ukraine delivery lane: withinUkraine (weekly batch, 7–14 days) or\nfromUsa (direct from the USA, 7–10 days). Fills `shipping` when that\nis omitted; an explicit `shipping` always wins."New value: +"Ukraine delivery lane: withinUkraine (weekly batch) or fromUsa (direct\nfrom the USA) — each answers its `np_eta` window for a recipient whose\npostal code we do not know. Fills `shipping` when that is omitted; an\nexplicit `shipping` always wins."
  2. Changed2 schema fields changed
    • changedInput schema / properties / shipping / description
      Previous value: -"Delivery: pickup | us | ukraine | international. If omitted, inferred from\ndestination_country (apostille legs default to US shipping)."New value: +"Delivery: pickup | us | ukraine | ukraine_direct | international. If\nomitted, inferred from destination_country (apostille legs default to\nUS shipping) or from `ua_lane` (fromUsa ⇒ ukraine_direct)."
    • addedInput schema / properties / ua_lane
      Added value: +{
      +  "default": null,
      +  "description": "Ukraine delivery lane: withinUkraine (weekly batch, 7–14 days) or\nfromUsa (direct from the USA, 7–10 days). Fills `shipping` when that\nis omitted; an explicit `shipping` always wins.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Staged day estimates — ranges, never guarantees.",
      +  "properties": {
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "howToProceed": {
      +      "type": "string"
      +    },
      +    "service": {
      +      "type": "string"
      +    },
      +    "stages": {
      +      "items": {
      +        "properties": {
      +          "businessDays": {
      +            "type": "integer"
      +          },
      +          "calendarDaysHigh": {
      +            "type": "integer"
      +          },
      +          "calendarDaysLow": {
      +            "type": "integer"
      +          },
      +          "note": {
      +            "type": "string"
      +          },
      +          "stage": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "stage"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "tier": {
      +      "type": "string"
      +    },
      +    "typicalTotalDaysHigh": {
      +      "type": "integer"
      +    },
      +    "typicalTotalDaysLow": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "service",
      +    "stages",
      +    "typicalTotalDaysLow",
      +    "typicalTotalDaysHigh",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.4/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 still adds real behavior: results are ranges not guarantees, and an unknown `tier` silently falls back to the standard figure rather than erroring. That fallback/error semantics is exactly the kind of trait an agent needs and annotations cannot express. Return shape is left to the output schema, which is a minor omission only.

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-loaded with the core calculation, then the usage rule, then parameter notes — no wasted sentences. The parameter list is slightly compressed into comma-separated fragments, which is dense but still parseable.

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 return values needn't be explained, and annotations cover safety. The description covers what is computed, when to use it instead of the sibling, and the one surprising behavior (silent tier fallback), leaving nothing essential out for a 5-param read-only 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 description coverage is 100% and each parameter's schema text already documents tiers, lanes, and the shipping inference precedence. The description restates service examples and the ua_lane-when-shipping-omitted rule without adding syntax or constraints beyond the schema, so 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?

States a specific verb and resource — computing a turnaround estimate as staging days plus mailing/delivery legs — and explicitly disambiguates from search_availability, which handles exact appointment times. An agent can distinguish it from every sibling without opening the schema.

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

Usage Guidelines5/5

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

"Use when the customer asks how long" gives the triggering condition, and "exact appointment times come from search_availability" names the alternative and its selecting condition. It also sets expectation that output is a range, never a guarantee, so the agent knows not to promise dates.

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