Skip to main content
Glama

Andrii Co. Notary & Apostille Assistant

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_price_quote"
  }
}

Input 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 from the USA: a flat $25, NP postage included).
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 ($25/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

NameRequiredDescriptionDefault
currencyYes
lineItemsYes
amountCentsYes
howToProceedYes
prepaymentRequiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / translation_docs / description
      Previous value: -"Apostille documents translated in Ukraine ($20/doc; the first doc is\nfree on the direct lane)."New value: +"Apostille documents translated in Ukraine ($25/doc; the first doc is\nfree on the direct lane)."
    • changedInput schema / properties / ua_lane / description
      Previous value: -"Ukraine delivery lane: withinUkraine (weekly batch, included) or\nfromUsa (direct: NP postage estimate + the $25 dispatch fee)."New value: +"Ukraine delivery lane: withinUkraine (weekly batch, included) or\nfromUsa (direct from the USA: a flat $25, NP postage included)."
  2. 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"
      +  ]
      +}
  3. 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"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint false and openWorldHint false, so "pure, no side effects, nothing booked" is somewhat redundant but reinforces the safety profile. The description adds genuine value by disclosing the failure mode when `apostille` is true and `tier` is invalid, and the cross-parameter rule that `tier` is ignored otherwise.

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?

It is front-loaded with the purpose and trigger before the parameter detail, and every clause carries information. The second half is a dense semicolon-separated run that risks being read as a wall of text, 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 an 8-parameter, all-optional pricing tool with full schema coverage, annotations and an output schema, the description covers trigger, side-effect profile, parameter interactions and the one error condition. Nothing an agent needs to call it correctly is missing, and return values are properly left to the output schema.

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 description coverage is 100%, so per-parameter definitions are handled; the baseline would be 3. The description earns above baseline by supplying cross-field semantics absent from the schema — the apostille/tier dependency, the already-certified case for needs_notarization, and the pricing role of ua_lane and translation_docs.

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 opening clause names a specific verb and resource — "Calculate a server-authoritative USD price estimate" — which is far more precise than the tool name alone. It is clearly a pricing/quote operation rather than a booking one. The only gap is that the sibling `request_price_match` also concerns pricing and the description never draws the line between them.

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?

"Use when the customer asks about cost" plus "before shipping" gives a clear trigger condition and sequencing relative to order placement. It also conditions several parameters (needs_notarization false for certified records, tier irrelevant when apostille is false). No explicit exclusions are stated, so an agent could still wonder whether `request_price_match` or `get_turnaround_estimate` is the better first call.

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