Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

by net.andrii
OverviewDiscussionsAdmin

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. Returns staged day estimates; an unknown tier falls back to the standard figure, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoApostille speed tier when service is apostille: expedited | priority | standard.
serviceYesService: notarization | apostille | apostille_mail | loan_signing.
shippingNoDelivery: pickup | us | ukraine | international. If omitted, inferred from destination_country (apostille legs default to US shipping).
destination_countryNoDestination country (used to infer shipping when `shipping` is omitted).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNo
stagesYes
serviceYes
disclaimerYes
howToProceedNo
typicalTotalDaysLowYes
typicalTotalDaysHighYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description adds meaningful behavioral context beyond the readOnly/destructive annotations: results are ranges, never guarantees; returns are staged day estimates; and an unknown tier falls back to the standard figure rather than erroring. These are non-obvious behaviors an agent must know before invoking the tool.

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 compact and front-loaded: the primary purpose and core behavioral caveat appear first, followed by a concise parameter list and the fallback behavior. Every sentence adds useful information; there is no filler or repetition of schema defaults.

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 estimation tool with four parameters, full schema coverage, and an output schema, the description covers the essential context: what it computes, how to use it, how it differs from the exact-availability tool, and what happens with invalid tier input. Nothing an agent needs to invoke it correctly is missing.

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 met. The description adds extra semantic value by giving concrete service examples, noting the fallback behavior for unknown tier values, and framing the parameters as contributing to 'processing days plus mailing and delivery legs.' This goes slightly beyond the schema's property descriptions.

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 opens with a specific verb and object ('Calculate typical turnaround') and clearly defines the resource as an estimate of apostille processing plus mailing/delivery legs. It also distinguishes itself from search_availability, which provides exact appointment times, so an agent can tell them apart immediately.

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?

The description explicitly states when to use the tool ('Use when the customer asks how long') and when not to rely on it ('exact appointment times come from search_availability'). This gives clear decision criteria and names the alternative tool, leaving no ambiguity about selection.

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 toolsInspect
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