Skip to main content
Glama

PapeleoYa — certified & sworn translations in Europe

Check translation & apostille requirements

check_document_requirements
Read-onlyIdempotent

Whether a foreign document needs a certified translation for an authority in Spain, Germany, France, Italy, Portugal, Sweden, Denmark, Norway or Finland, who may certify it there, and whether it needs an apostille or consular legalisation given the country that issued it. Answers come only from PapeleoYa network guides (with links); anything they do not cover is returned as "unknown" with the closest guide. Use for questions like "Do I need a sworn translation of my Moroccan birth certificate for Spanish citizenship?" or "Apostille or legalisation for Pakistani documents in Norway?".

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": "check_document_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoDocument kind.
procedureNoWhat the document is for, e.g. "residence permit", "citizenship", "marriage", "degree recognition", "driving licence exchange", "family reunification".
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".
origin_countryNoCountry that ISSUED the document (name or ISO code), e.g. "Morocco", "PK".
document_languageNoLanguage the document is written in (code or English name), if known.

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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that, the description discloses data provenance ('answers come only from PapeleoYa network guides (with links)') and the important fallback that uncovered cases return 'unknown' plus the closest guide — genuinely useful behavior an agent could otherwise misread as a failure.

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?

Two dense sentences followed by example questions; there is little waste and the core question is front-loaded. The nine-country list is long and partly redundant with the destination parameter description, which costs it a point.

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 five-parameter, read-only lookup with no output schema, the description covers scope, provenance, the 'unknown' fallback outcome, and the link-bearing return, which is what an agent needs to interpret results. Nothing material is left unstated apart from exact response shape, which is not required here.

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 the schema already defines all five parameters, including the destination-vs-origin_country distinction and the document enum. The description reinforces the destination/origin framing but adds no new syntax, format, or constraint details beyond the schema, so the baseline of 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-plus-resource: deciding whether a foreign document needs a certified translation, who may certify it, and whether an apostille or consular legalisation applies, across nine named destination countries. It is clearly distinct from siblings like get_translation_quote and start_order because it answers a requirements question rather than pricing or ordering.

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 explicit use context ('Use for questions like ...') with two concrete example questions spanning translation and apostille, and implicitly bounds scope to the nine listed destinations. It does not name a sibling alternative for out-of-scope destinations or for pricing/ordering needs, so routing away from get_translation_quote or start_order still requires the agent to infer that those exist.

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