Skip to main content
Glama

PapeleoYa — certified & sworn translations in Europe

Get a certified translation price

get_translation_quote
Read-onlyIdempotent

Exact price of a certified / sworn / official translation (traducción jurada, beglaubigte Übersetzung, traduction assermentée, traduzione giurata, tradução certificada, auktoriserad översättning…) of personal documents for use in Spain, Germany, France, Italy, Portugal, Sweden, Denmark, Norway or Finland. Use it whenever someone asks how much a certified translation costs, or needs one for a visa, residence permit, citizenship, marriage, degree recognition or driving-licence exchange. Returns the total in local currency with VAT, line items, turnaround, what is included (e.g. apostille translation), the PapeleoYa network site that fulfils the order and a link to it. Prices are computed with each site's live price list.

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>",
      "source_language": "<source_language>",
      "documents": "<documents>"
    },
    "name": "get_translation_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
urgentNoExpress / urgent delivery (only for small orders and common languages).
ship_toNoItaly only: where the sworn paper original is couriered.italy
documentsYesOne entry per document.
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".
paper_originalNoFrance, Portugal and the Nordics: add a stamped paper original by post. (Germany and Italy always include one.)
source_languageYesLanguage the document is written in: ISO 639-1 code or English name, e.g. "en", "Arabic", "uk".
target_languageNoLanguage to translate into. Default: the destination country's official language (Spanish for Spain, German for Germany…).

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new context: quotes include VAT in local currency, line items, turnaround, inclusions, the fulfilling network site, and a link, all computed from live price lists. It does not mention caching, volatility of quotes, or failure modes for unsupported destinations, which keeps it from a 5.

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-loaded with the core purpose and price-per-country context before the usage triggers and return payload. The multilingual synonym list is long but serves a real disambiguation purpose; the passage could still be tightened slightly.

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 steps in and enumerates what a quote returns (total with VAT, line items, turnaround, inclusions, fulfilling site, link). Combined with a fully documented 7-parameter schema, an agent has everything needed to call it and interpret the result.

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 parameters — destination, source_language, target_language default, documents with pages and has_apostille, urgent, paper_original, ship_to — are already fully documented with defaults and edge-case rules. The description adds no parameter-level meaning beyond the country scope implied by 'destination', 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 specific verb and resource ('exact price of a certified/sworn/official translation') and delimits scope precisely: personal documents used in nine named countries. The query-trigger framing ('whenever someone asks how much a certified translation costs') makes clear this is a pricing tool, distinct from requirement-checking or order-starting siblings.

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?

Gives concrete when-to-use triggers — cost questions, visas, residence permits, citizenship, marriage, degree recognition, driving-licence exchange. It does not explicitly name a when-not condition or point to start_order for acting on the quote, so it stops just short of full alternative 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.

Resources