Skip to main content
Glama
Sign In

Translayte

by com.translayte
OverviewDiscussionsAdmin

Create an unpaid order

create_order

Places an unpaid order for the customer from the same arguments as get_quote plus their name, email and E.164 phone. The response carries signed links: pay_url is our payment page (card, PayPal, Google Pay, Apple Pay) to give the customer, status_url shows the order and collects any missing documents. Links last 48 hours. A customer whose email already has an account receives the links by email instead, and the response says so: tell them to check their inbox. Documents can be sent first with send_document, or uploaded by the customer at the status_url after paying when you create the order from a page count. Pass idempotency_key so a retry never places a second order.

Input Schema

NameRequiredDescriptionDefault
nameYesThe customer's full name
emailYesThe customer's email address
notesNoAnything the translator should know: names to keep, the purpose, formatting wishes.
phoneYesThe customer's phone number in E.164 format, e.g. +14155552671
speedNostandard, next_day (+25%) or same_day (+100%)
currencyNoThe currency to quote in; each is its own price sheet. Defaults to GBP.
quantityNoPages to translate (a page is up to 250 words). Optional when file_tokens are given: the documents are measured instead, and a quantity can only raise the measured count.
file_tokensNoTokens from send_document for the documents to translate.
certificationNoOmit for standard; the response lists every option the pair offers with its total.
country_of_useNoISO 3166-1 alpha-2 code of the country the translation is for, e.g. ES for a sworn translation for Spain.
idempotency_keyNoYour own unique key for this order attempt; a retry with the same key within a day returns the order already placed instead of a second one.
source_languageYesSource language code from list_languages, e.g. en-gb
target_languageYesTarget language code from list_languages, e.g. es
customer_countryNoISO 3166-1 alpha-2 code of the customer's country. Outside GB no VAT is charged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With only openWorldHint in annotations, the description carries the burden well. It discloses that links expire after 48 hours, that pay_url is the payment page and status_url collects documents, that existing-email customers receive links by email instead, and that idempotency_key prevents duplicate orders on retry.

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?

The description is front-loaded with the core action and response behavior, and nearly every sentence earns its place by explaining links, email fallback, document flow, or idempotency. It is dense as a single paragraph and one sentence about document upload timing is slightly convoluted, but overall it is efficient.

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 complex 14-parameter mutation with no output schema, the description covers the essential context: customer identity, quote-derived arguments, payment and status links, 48-hour expiry, email fallback, document handling, and duplicate-order prevention. An agent has enough detail to invoke it correctly and explain next steps to the customer.

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%, so the schema already documents all 14 parameters in detail. The description adds a useful relationship to get_quote and send_document, but most parameter-level details such as E.164 phone, file_tokens, quantity, and idempotency_key are already covered by the schema.

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: "Places an unpaid order for the customer." It also distinguishes the tool from get_quote by explaining that create_order takes the same arguments plus customer identity details, so an agent can understand exactly what this tool does.

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 description gives clear workflow guidance: send documents first with send_document, or let the customer upload them at status_url after paying when creating from a page count. It also explains the email-account case and idempotency-key retry behavior. It does not explicitly say when not to use this tool, but the operational context is strong.

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

All Translayte 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