Skip to main content
Glama
Sign In
PageTranslate MCP Server

PageTranslate MCP Server

Official
by Caravaca-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Upload a document and get a translation quote

upload_document

Upload a local PDF, DOCX, EPUB, or image to get an exact translation price before starting or paying; uploads are free and return job ID, word count, and next steps.

Instructions

Upload a local PDF (text or scanned), DOCX, EPUB or image (PNG, JPG, WEBP, TIFF, BMP, GIF) to PageTranslate and get the exact price to translate it. Uploading is free and does not start or charge anything. Returns job_id, word count, price and what to do next. Max 100 MB and 1,000 PDF pages; uploads are rate limited per account.

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": {
      "file_path": "<file_path>",
      "target_language": "<target_language>"
    },
    "name": "upload_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path of the file on this computer.
target_languageYesLanguage code to translate into, e.g. es, fr, de, it, ja, ko, ar, hi, ru. Special codes: pt (Portugal) or pt-BR (Brazil), zh (Simplified) or zh-TW (Traditional), fil (Filipino), no (Norwegian).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnly=false, openWorld=true, idempotent=false, destructive=false; the description goes well beyond them by disclosing the cost model (free, no charge, no job started), hard limits (100 MB, 1,000 PDF pages), and per-account rate limiting. These are exactly the operational constraints an agent needs before invoking an upload.

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?

Four tight sentences, each carrying distinct information: capability and formats, cost safety, return shape, and limits. Nothing is repeated and the key non-committal guarantee is front-loaded before the constraints.

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?

With no output schema, the description compensates by naming the returned fields (job_id, word count, price, next steps). Combined with annotations covering side-effect profile and the description covering cost and limits, an agent has everything needed to call this correctly.

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%, with file_path and target_language fully documented including language-code special cases. The description's format list loosely maps to file_path but adds no new meaning beyond the schema, 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?

States a specific verb (upload) and resource (document) plus the exact supported formats and the concrete outcome: a translation price quote. The clause 'does not start or charge anything' implicitly separates it from start_translation, so an agent can route correctly without opening another 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?

Gives clear context for when to call: to obtain a price before committing, with the assurance that it is free and non-committal. It stops short of explicitly naming start_translation as the follow-up step or stating when-not to use it, so routing to the sibling is inferred rather than directed.

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

Deploy Server

Other Tools