Skip to main content
Glama

Translate a resume

translate_resume

Translate a resume into another language as a NEW inactive copy named after the language; the original resume is not changed. Skill level and category and language name and proficiency stay fixed English keys, which the rendered resume shows in its language. Runs asynchronously — returns a task_id immediately and a message is posted into the user's chat when the copy is ready or the translation fails; get_task_status(task_id) reports progress and the outcome. Consumes one resume translation from the user's plan. If this resume was already translated into that language, returns the existing copy with status 'reused' and spends nothing. target_language is one of: en_EN, ru_RU, es_ES, pt_BR, de_DE, fr_FR, it_IT, tr_TR, hi_IN, uk_UA, id_ID, ja_JP. When the user asked for more than the translation, pass the rest as follow_up_instruction: the ready message offers it on the new copy with one tap. Returns 'not_found' if the resume does not belong to the current user, 'already_in_language' if the resume is already written in that language, 'limit_exceeded' naming the day it frees up if the plan quota is reached, and 'invalid_payload' for an unknown language code.

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": {
      "input": "<input>"
    },
    "name": "translate_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
statusYes'processing' — the translation runs asynchronously; 'reused' — the copy exists.
task_idNoBackground task id, or null when an existing copy was reused.
resume_idNoId of the translated copy: set now when reused, otherwise it arrives with the chat message.
source_resume_idYesId of the resume being translated; it is not changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / TranslateResumeInput / properties / target_language / description
      Previous value: -"Locale code of the language to translate into, e.g. 'en_EN', 'de_DE', 'es_ES'."New value: +"The language to translate into: a locale code ('de_DE'), a language code ('de', 'de-AT', 'en_US') or its English name ('German')."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare a non-readonly, non-idempotent, non-destructive mutation, and the description adds substantial beyond that: asynchronous execution with a task_id, a chat message on success or failure, and consumption of one translation from the user's plan quota. The only thing not covered is whether the new copy inherits all sections/settings verbatim, but the quota and async disclosure is well above the annotation baseline.

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?

Front-loaded with the core action and the original-is-unchanged guarantee, then sequenced into async behavior, quota, reuse, language list, and error codes. Dense but every sentence carries operational information; the trailing error-code enumeration is list-like but earns its space since these are decision-relevant outcomes.

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?

For an asynchronous, quota-consuming mutation with an output schema, the description supplies everything an agent needs before calling: what happens immediately (task_id), what happens later (chat message), how to poll (get_task_status), what it costs, and the full set of failure statuses including not_found and limit_exceeded.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema carries no enums and only thin descriptions, so the description does the heavy lifting: it enumerates the twelve accepted target_language locale codes and maps an unknown code to 'invalid_payload'. It also explains follow_up_instruction's purpose and downstream effect (offered on the new copy with one tap) beyond the schema's 'rest of the user's request'.

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 and resource (translate a resume) and immediately defines the output artifact: a NEW inactive copy named after the language, with the original unchanged. That scope statement plus the async note lets an agent distinguish it from siblings like create_resume_version or request_resume_update.

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

Usage Guidelines5/5

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

Explicitly covers the reuse case ('already translated into that language, returns the existing copy with status reused and spends nothing'), routes progress checks to get_task_status(task_id), and tells the agent how to handle multi-part user requests via follow_up_instruction. It is essentially a when-to-use and what-to-expect contract.

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.