Skip to main content
Glama
everbary

eVerbary MCP server

Official
by everbary
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Place a certified translation order

create_order
Idempotent

Place a certified translation order with uploaded files: preview price and delivery first, then confirm to queue it for payment.

Instructions

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.

Input Schema

TableJSON 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, only some languages and 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. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the order is placed unpaid and enters the translation queue, payment is handled separately, and the call is refused when the key's spending limits are exceeded. This complements idempotentHint=true (reassured by the request_id note) and destructiveHint=false without contradicting them.

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?

Four sentences, no filler, and the critical confirm=false-first instruction is front-loaded. Every sentence carries either the flow, the state transition, the payment path, or the failure condition.

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?

With no output schema, the description still tells the agent what the preview contains (price, delivery, files), what state the order lands in (unpaid, queued), and how to complete payment. Nothing an agent needs to invoke or continue the workflow 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 92%, so most parameter meaning is already documented. The description nonetheless adds procedural semantics for confirm and request_id (preview-then-confirm, retry safety) and the preview contents, going beyond the field-level text.

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 and resource ('Place a certified translation order') plus scope ('for this account with the uploaded files'). It is clearly distinguishable from siblings like get_quote, pay_order, and order_status, which cover quoting, payment, and tracking rather than order creation.

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?

Gives an explicit two-step protocol: call with confirm=false and show the preview, then call again with confirm=true and a request_id. It also names the follow-up alternatives, pay_order or sharing the payment link, so the agent knows what to do after this tool returns.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools