Skip to main content
Glama

Batch Evaluate Translations

xcomet_batch_evaluate
Read-onlyIdempotent

Batch evaluate multiple translation pairs to obtain aggregate quality scores and per-segment error analysis, enabling efficient comparison of translation system outputs.

Instructions

Evaluate multiple translation pairs in a batch.

This tool processes multiple source-translation pairs and provides aggregate statistics along with individual results.

Args:

  • pairs (array): Array of translation pairs, each with:

    • source (string): Original source text

    • translation (string): Translated text

    • reference (string, optional): Reference translation

  • source_lang (string, optional): Source language code

  • target_lang (string, optional): Target language code

  • response_format ('json' | 'markdown'): Output format (default: 'json')

  • use_gpu (boolean, optional): Use GPU for inference if available (default: false)

  • batch_size (number, optional): Inference batch size, 1-64 (default: 8). Larger = faster but uses more memory.

Returns: { "average_score": number, "total_pairs": number, "results": [ { "index": number, "score": number, "error_count": number, "has_critical_errors": boolean } ], "summary": string }

Examples:

  • Evaluate entire translated document

  • Compare MT system quality across test set

  • Identify segments needing attention

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairsYesArray of translation pairs to evaluate
source_langNoSource language code
target_langNoTarget language code
response_formatNoOutput formatjson
use_gpuNoUse GPU for inference (faster if available). Default: false (CPU only)
batch_sizeNoBatch size for GPU processing (1-64). Larger = faster but uses more memory. Default: 8

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
average_scoreYesAverage quality score across all pairs
total_pairsYesTotal number of evaluated pairs
resultsYesIndividual results for each pair
summaryYesOverall quality summary
Behavior4/5

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

Adds value beyond annotations by detailing GPU usage, batch size limits, and memory implications; no contradictions.

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?

Well-structured with sections, front-loaded purpose, but somewhat verbose; could trim repetitive parameter details.

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?

Fully covers all aspects given 6 params, output schema, and annotations; no gaps in usage or behavior.

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 already covers parameters well; description adds extra context like batch size range and examples, going beyond schema.

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?

Clearly states the tool evaluates multiple translation pairs in a batch, distinguishing it from single-pair evaluate and error detection siblings.

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?

Provides examples and context but lacks explicit comparison to alternatives for when to choose batch vs single evaluate or detect-errors.

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/shuji-bonji/xcomet-mcp-server'

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