Skip to main content
Glama

PapeleoYa — certified & sworn translations in Europe

List countries, languages and prices

list_services
Read-onlyIdempotent

What PapeleoYa offers: the countries served (Spain, Germany, France, Italy, Portugal, Sweden, Denmark, Norway or Finland), which network site fulfils each, the languages translated with their price tier and "from" price, document types, what is included (apostille translation, signed PDF, paper original), urgent options and turnaround. Call without a country for an overview of all countries, or with one for its full language and price list. Use it when someone asks whether a language or country is covered, or what a certified translation includes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationNoCountry 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".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value beyond that by enumerating exactly what the catalog returns and how the optional parameter changes the breadth of the response (all countries vs. one country's full list).

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?

Content is front-loaded with what the tool surfaces, followed by calling modes and triggers; no sentence is filler. It is a dense single paragraph, so the two calling modes would be easier to scan as separate sentences, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single optional parameter, no output schema and already-rich annotations, the description covers what an agent needs: what the response contains, how the parameter changes it, and when to reach for the tool. It does not state anything about price caveats or response shape, a minor gap given there is no output schema.

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 100% and already explains the 'destination' parameter as the country of use. The description adds behavioral meaning the schema does not: omitting it yields an all-country overview, while providing it yields that country's full language and price list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name 'list_services' is generic, but the description immediately names the concrete payload: countries served, fulfilling network site, languages with price tiers and 'from' prices, document types, inclusions, urgent options and turnaround. That makes it distinguishable from a pricing/quote tool in the sibling set, though no sibling is named explicitly.

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?

It gives clear triggering conditions ('when someone asks whether a language or country is covered, or what a certified translation includes') and explains the two calling modes: omit the country for an overview, supply one for its full language and price list. It stops short of naming an alternative such as a quote tool for actual pricing calculations.

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