Skip to main content
Glama

eVerbary Certified Translations

Get a price quote

get_quote
Read-onlyIdempotent

Price and delivery time for a certified translation, for this account (its team discount and included rush applied), with the other turnarounds for comparison and whether the key's spending limits allow it. Nothing is ordered.

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": {
      "language_from": "<language_from>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoCertified pages (up to 250 words each). Leave out when passing upload_ids: the files' pages are counted.
turnaroundNostandard; expedited (+20% of the page total, about half the time); expedited_plus (+40%, same day, any language pair, 8 AM-4:59 PM Eastern). Teams may have rush included.standard
upload_idsNoupload_id values from upload_document, to count pages from the files.
language_toNoLanguage code from list_languages, e.g. 'spanish', 'portugueseBrazil', 'english'.english
notarizationNoAdd a notarized certificate.
language_fromYesLanguage code from list_languages, e.g. 'spanish', 'portugueseBrazil', 'english'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / turnaround / description
      Previous value: -"standard; expedited (+20% of the page total, about half the time); expedited_plus (+40%, same day, only some languages and 8 AM-4:59 PM Eastern). Teams may have rush included."New value: +"standard; expedited (+20% of the page total, about half the time); expedited_plus (+40%, same day, any language pair, 8 AM-4:59 PM Eastern). Teams may have rush included."
  2. First observed

TDQS

A3.9/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 a closed world, so the safety profile is fully covered. The description adds genuinely useful behavior: the quote is account-specific, applies the team discount and included rush, and reports whether spending limits permit the order. It does not mention cost of repeated calls, error cases, or how limits are evaluated.

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?

Two sentences, front-loaded with the resource and result, and the negative guarantee ('Nothing is ordered') placed last for emphasis. The first sentence is dense and reads as a run-on, but no sentence is filler.

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 six parameters fully documented in the schema and no output schema, the description covers the return content well: price, delivery time, the other turnarounds for comparison, and spending-limit status. Adequate for a read-only quote tool, though nothing is said about failure modes such as unsupported language pairs.

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 carries its own enum, default and constraints, so the schema does the heavy lifting. The description contributes only that the account's team discount and included rush are already applied to the turnaround pricing, which slightly clarifies how the turnaround parameter is evaluated but adds no syntax or format detail.

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 resource (price and delivery time for a certified translation) with explicit scope (this account, team discount and included rush applied), and closes with 'Nothing is ordered', which separates it cleanly from create_order/pay_order. An agent can pick it out of the sibling list 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?

The 'Nothing is ordered' clause makes the quote-before-ordering context clear, and the mention of spending limits signals when the result is actionable. It stops short of naming create_order or stating exclusions explicitly, so it is clear context rather than full when/when-not routing.

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.