Skip to main content
Glama

PapeleoYa — certified & sworn translations in Europe

Get the order link

start_order
Read-onlyIdempotent

Link to order a certified / sworn translation on the right PapeleoYa network site for Spain, Germany, France, Italy, Portugal, Sweden, Denmark, Norway or Finland, pre-filled with the language pair and document where that site supports it. The user uploads the documents and pays on that site; this tool never receives documents or personal data. Use it when the user wants to go ahead after a quote.

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": {
      "destination": "<destination>"
    },
    "name": "start_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
urgentNoUrgent delivery wanted.
documentNoMain document kind.
destinationYesCountry where the translated document will be USED (submitted to an authority): Spain, Germany, France, Italy, Portugal, Sweden, Denmark, Norway or Finland. Name or ISO code, e.g. "Spain" or "ES".
has_apostilleNoThe document carries an apostille / legalisation to translate.
source_languageNoLanguage the document is written in (code or English name).
target_languageNoLanguage to translate into. Default: the destination's official language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond the readOnly/idempotent annotations: the user uploads and pays on the target site, the tool never receives documents or personal data, and pre-fill only happens "where that site supports it". This discloses the hand-off boundary and a partial-support caveat that annotations cannot express.

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?

Front-loads what the tool returns, then the hand-off mechanics, then the trigger condition. The nine-country enumeration is somewhat redundant with the destination parameter but stays readable; no wasted sentences.

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 the return value (a link) and what the link is pre-filled with. Privacy boundary, payment location, and trigger condition cover everything needed to call this six-parameter tool correctly.

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 coverage is 100%, so all six parameters are already documented, including the destination/language defaults. The description only echoes the language-pair and document pre-fill behaviour without adding syntax or edge-case meaning, so baseline 3 applies.

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 concrete verb and resource: it returns a link to order a certified/sworn translation on the appropriate PapeleoYa network site. The country scope and the pre-fill behaviour make it unmistakable against get_translation_quote, check_document_requirements and list_services.

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?

Explicit when-to-use: "when the user wants to go ahead after a quote", which also implies it is not the tool for quoting or for requirement checking. No explicit when-not clause is given, but the conversion-point framing is clear enough to route an agent.

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