Skip to main content
Glama
lichman0405

PDF2ZH MCP Server

by lichman0405
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

translate_pdf

Translate PDF files while preserving formulas, charts, and layout. Outputs both translated-only and bilingual side-by-side PDFs.

Instructions

Translate a PDF file while preserving formulas and layout.

    Args:
        file: Path to the input PDF file.  Absolute paths are used
              as-is; relative paths are resolved against the shared
              workspace directory (~/.featherflow/workspace by default,
              overridable via WORKSPACE_DIR env var).
        lang_in: Source language code (e.g. "en", "auto" for auto-detect).
        lang_out: Target language code (e.g. "zh", "ja", "ko", "fr", "de").
        output_dir: Directory for output files. Defaults to the shared
                    workspace directory so that other MCP tools
                    (e.g. feishu-mcp upload_file) can access the outputs.

    Returns:
        A summary with absolute paths to the mono (translated-only) and
        dual (bilingual side-by-side) output PDF files.  These paths
        can be passed directly to feishu-mcp upload_file / upload_file_and_share.

    Environment variables that control the LLM used for translation:
        OPENAI_BASE_URL – API base URL
        OPENAI_API_KEY  – API key
        OPENAI_MODEL    – Model name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYes
lang_inYes
lang_outYes
output_dirNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.1/5.0
Behavior4/5

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

With no annotations, the description fully bears the transparency burden. It discloses that the tool preserves formulas and layout, uses an LLM controlled by environment variables, returns absolute paths, and produces two output files. It does not mention any destructive actions or limitations, but it is sufficiently transparent for a translation tool.

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?

The description is well-structured with an 'Args' and 'Returns' section, front-loading the main purpose. It contains several sentences but each earns its place by providing necessary context. Slight improvement could condense some details, but it is not overly verbose.

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?

Given the 4 parameters, no output schema (though description covers returns), and sibling tool presence, the description covers input handling, output paths, integration hints, and environment variables. It lacks explicit error handling or size limits, but overall it provides a complete picture for usage.

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?

The input schema has 0% description coverage, so the description must add meaning. It does so by explaining path resolution logic (absolute vs relative), providing example language codes, and describing the output directory's default and purpose. This adds significant value beyond the schema's bare type definitions.

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?

The description clearly states the tool's purpose: 'Translate a PDF file while preserving formulas and layout.' This is a specific verb+resource combination that distinguishes it from the sibling tool 'list_supported_languages'.

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?

The description provides context about path resolution, environment variables, and output directory integration with other MCP tools, but it does not explicitly state when to use this tool versus alternatives or when not to use it. It mentions the sibling tool's existence only through context, not in guidelines.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lichman0405/pdftranslate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server