A punt · Aranese (Val d'Aran Occitan)

Tradusir en aranés

tradusir_aranes

Read-onlyIdempotent

Translate between Aranese (oc) and Spanish (es) or Catalan (ca): es→oc, ca→oc, oc→es, oc→ca. Machine translation with A punt's own corrections; for important texts, check the result with corregir_aranes.

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": {
      "text": "<text>",
      "de": "<de>",
      "a": "<a>"
    },
    "name": "tradusir_aranes"
  }
}

Input Schema

Name	Required	Description
`a`	Yes	Target language: oc (Aranese), es or ca. One of the two must be oc.
`de`	Yes	Source language: es (Spanish), ca (Catalan) or oc (Aranese).
`text`	Yes	Text to translate (max 5,000 characters).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.2/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 safety is covered. The description adds real behavioral context beyond them: output is machine translation (not authoritative) with A punt's own corrections, and a verification step is recommended. It omits error behavior and whether input character limits are enforced, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler: the supported directions are front-loaded and the caveat plus sibling pointer come second. Nothing could be removed without losing information.

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?

For a 3-parameter read-only tool with a fully described schema and rich annotations, the description covers purpose, directions, quality caveat and next step. It does not indicate what the response contains (no output schema exists), but that is a minor gap rather than a blocking one.

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% and both enum parameters already document oc/es/ca and the 'one must be oc' constraint. The description's direction list restates that constraint in a more usable form but adds no new syntax or format detail, so the 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?

Names a specific verb and resource (translate text) and enumerates the exact language-direction pairs supported: es→oc, ca→oc, oc→es, oc→ca. An agent can distinguish it from corregir_aranes (correction) and diccionari_aranes (dictionary) without opening any schema.

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?

Explicitly routes the agent to a named sibling with a condition: 'for important texts, check the result with corregir_aranes.' That is concrete when-to-use guidance. It does not cover when not to use it (e.g. for single-word lookups where diccionari_aranes fits), so it stops short of full 5-level guidance.

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

All A punt · Aranese (Val d'Aran Occitan) tools Inspect

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

Need Help?