Skip to main content
Glama

eVerbary Certified Translations

Place a certified translation order

create_order
Idempotent

Place a certified translation order for this account with the uploaded files. Call first with confirm=false and show the preview (price, delivery, files) to the user; then call again with confirm=true and a request_id. The order is placed unpaid and enters the translation queue; pay it with pay_order or share the payment link. Refused when over the key's spending limits.

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>",
      "upload_ids": "<upload_ids>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoInstructions for the translators (spelling of names, which pages...).
pagesNoCertified pages. Leave out to use the pages counted in the files.
confirmNofalse: preview only. true: place the order (after showing the preview to the user).
request_idNoRequired with confirm=true: a unique string for this order (e.g. a UUID). Retrying with the same request_id never creates a second order.
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_idsYesupload_id values returned by upload_document, one per file.
case_numberNoThe client's case or matter number; printed on the invoice.
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'.
client_last_nameNo
client_first_nameNoThe firm's client (whose documents these are), if any.

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

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important side effects: the order is placed unpaid, enters the translation queue, and is paid later via pay_order or a payment link. It also states that calls are refused when over the key's spending limits, which is useful operational context not covered by the annotations.

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 four tight sentences and is front-loaded with the main action. Every sentence adds actionable workflow or side-effect context without repeating the title verbatim.

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 12-parameter mutation with no output schema, the description covers the critical invocation flow, preview contents, unpaid order state, queue entry, payment next step, and spending-limit refusal. The remaining parameter details are well covered by the high-coverage input schema and annotations.

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 92%, so the schema already explains nearly all parameters, including confirm, request_id, upload_ids, and turnaround. The description reinforces the confirm/request_id flow but adds little parameter meaning beyond what the schema provides.

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 states a specific verb and resource: 'Place a certified translation order' for the account using uploaded files. It also distinguishes the ordering step from payment by directing the user to pay_order or a payment link afterward.

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?

It gives a clear two-step workflow: first call with confirm=false to show the preview, then call with confirm=true and a request_id. It also names the payment follow-up and a spending-limit refusal condition, but does not explicitly address alternatives such as get_quote.

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.