Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

by net.andrii
OverviewDiscussionsAdmin

get_price_quote

Read-only

Calculate a server-authoritative USD price estimate before shipping — pure, no side effects, nothing booked. Use when the customer asks about cost. Accepts: document_count, mobile, after_hours, apostille plus tier (e.g. expedited, priority, standard, mailin); set needs_notarization false for already-certified records; ua_lane (withinUkraine | fromUsa) prices the Ukraine direct lane, translation_docs the in-Ukraine translation. Returns amountCents and line items; fails if apostille is true and tier is invalid (with apostille false, tier is ignored).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tierNoApostille tier when `apostille`: expedited | priority | standard | mailin.
mobileNoTrue if we travel to the customer (adds the flat travel fee).
ua_laneNoUkraine delivery lane: withinUkraine (weekly batch, included) or fromUsa (direct: NP postage estimate + the $25 dispatch fee).
apostilleNoTrue to include a Secretary-of-State apostille.
after_hoursNoMobile only: the chosen slot is after 6pm or on a weekend.
document_countNoNumber of documents (1–20). Default 1.
translation_docsNoApostille documents translated in Ukraine ($20/doc; the first doc is free on the direct lane).
needs_notarizationNoSet false for a mail-in apostille of already-certified public records (birth/marriage/death certificates) that need no notarial act.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYes
lineItemsYes
amountCentsYes
howToProceedYes
prepaymentRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / translation_docs
      Added value: +{
+  "default": null,
+  "description": "Apostille documents translated in Ukraine ($20/doc; the first doc is\nfree on the direct lane).",
+  "format": "int64",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedInput schema / properties / ua_lane
      Added value: +{
+  "default": null,
+  "description": "Ukraine delivery lane: withinUkraine (weekly batch, included) or\nfromUsa (direct: NP postage estimate + the $25 dispatch fee).",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "amountCents": {
+      "type": "integer"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "howToProceed": {
+      "type": "string"
+    },
+    "lineItems": {
+      "items": {
+        "properties": {
+          "amountCents": {
+            "type": "integer"
+          },
+          "label": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "amountCents"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "prepaymentRequired": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "currency",
+    "amountCents",
+    "lineItems",
+    "prepaymentRequired",
+    "howToProceed"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, and the description reinforces this with 'pure, no side effects, nothing booked'. Beyond that it discloses a genuine error mode ('fails if `apostille` is true and `tier` is invalid') and the tier-ignored-when-apostille-false rule, which annotations cannot convey.

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?

Three dense sentences, front-loaded with purpose and safety, then parameters, then return/failure behavior. Efficient and well ordered, though the parameter sentence is long and list-like.

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?

With annotations covering safety and an output schema covering amountCents/line items, the description fills the remaining gaps: parameter interactions and failure conditions. The only omission is how it relates to request_price_match, a meaningful ambiguity given the sibling set.

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 baseline would be 3, but the description adds cross-parameter semantics the schema lacks: tier examples, the ua_lane choice and its pricing effect, the first-doc-free interaction of translation_docs with the direct lane, and the needs_notarization condition.

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+resource ('Calculate a server-authoritative USD price estimate') and immediately scopes it with 'pure, no side effects, nothing booked', which distinguishes it from the booking siblings. An agent can tell this is a pre-sale quote tool and not an action tool 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 Guidelines4/5

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

Gives a clear trigger: 'Use when the customer asks about cost.' However, it never addresses the obvious alternative in the sibling list, request_price_match, leaving the agent to guess which pricing tool to pick.

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