erp2pdf-studio-mcp

Overview Schema Source Related Servers Discussions Admin

get_translations

Retrieve all translatable strings for specified PDF or email templates. Access translations, translation status, glossary suggestions, and missing cell counts for every language.

Instructions

Every translatable string of a PDF template (kind=pdf, header and footer parts included) or an email template (kind=email: subject and body text), with its translation per target language, a status per language (translated, inherited, override, invalid, missing), glossary suggestions for missing cells and missing counts per language. A string that prints values keeps them as {{ placeholders }}; an email string keeps its inline tags (b, strong, i, em, u, a, span, code, br) as numbered placeholders <1>...</1> and <2/>, listed in placeholders (the element each stands for in tags).

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": {
      "template_id": "<template_id>"
    },
    "name": "get_translations"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No		pdf
`template_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Oct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it enumerates the status vocabulary (translated, inherited, override, invalid, missing), discloses that suggestions are glossary-based and only for missing cells, and explains the placeholder encoding rules for values and inline HTML tags. It never states that the call is a pure read or what happens for an unknown template_id, 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?

Two dense sentences that front-load the return payload before the placeholder mechanics. Every clause carries information, though the parenthetical placeholder explanation is heavy and could be tightened without loss.

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?

There is no output schema, so the description must describe return values, and it does so thoroughly down to the shape of the placeholders and tags fields. Given only two parameters and no annotations, the only real gap is the absence of any note on error behavior or empty/missing templates.

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 description coverage is 0%, so the description must compensate, and it does for the non-obvious parameter: kind=pdf is scoped to header and footer parts, kind=email to subject and body text. template_id is left unstated, though its meaning is self-evident from the tool name and required flag.

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 description names the exact resource (every translatable string of a PDF or email template) and the payload it returns (translations per language, status, suggestions, missing counts). It also implicitly separates the two modes via kind=pdf vs kind=email. It does not explicitly contrast itself with siblings like get_template or get_email_template, keeping it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the kind parameter values tell the agent which template family this applies to, and the presence of set_translations as a sibling implies this is the read side. There is no explicit statement of when to call this versus get_template/get_email_template, nor any prerequisite or exclusion.

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