Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

Train PyLaia Model

transkribus_pylaia_train

Initiate PyLaia HTR model training for a collection with optimized default parameters that improve model quality over server defaults. Customize training settings or use the provided defaults.

Instructions

Start PyLaia HTR model training for a collection. By default, sends training parameters matching the Transkribus UI defaults (textFeatsCfg with TextFeats preprocessing, use_masked_conv=True, max_epochs=100). Without these defaults, the server uses different preprocessing (trpPreprocPars) which produces significantly worse models. Set noTrainingDefaults=true to send no training parameters (server defaults).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collIdYesCollection ID
modelNameNoName for the new model
descriptionNoDescription of the model
baseModelIdNoBase model ID for transfer learning
providerNoTraining provider (default: "PyLaia")PyLaia
languageNoLanguage code (e.g. "rus", "deu", "eng")
trainListNoTraining page list
trainListFileNoAbsolute path to JSON file containing training page list array of {docId, pageId} objects. Example: /tmp/transkribus-training/train_list.json
testListNoTest page list
testListFileNoAbsolute path to JSON file containing test page list array of {docId, pageId} objects. Example: /tmp/transkribus-training/test_list.json
omitLinesByTagNoTags of lines to omit from training
reverseTextNoWhether to reverse text direction
imgTypeNoImage type
customAbbrevsTrainingNoEnable custom abbreviations training
customTagTrainingNoEnable custom tag training
trainPropertiesNoEnable training properties
textFeatsCfgNoTextFeats preprocessing config override. Merged with UI defaults (normheight=64, deslope/deslant=true, enh=true). Only specify fields you want to change.
createModelParsNoModel architecture parameters as key-value pairs (e.g. {"--rnn_units": "512"}). Merged with UI defaults (use_masked_conv=True, cnn_poolsize="2 2 0 2", etc.). Only specify parameters you want to override.
trainCtcParsNoCTC training parameters as key-value pairs (e.g. {"--max_epochs": "200"}). Merged with UI defaults (max_epochs=100, learning_rate=3.0E-4, batch_size=24, etc.). Only specify parameters you want to override.
max_epochsNoMaximum training epochs (default: 100). Shortcut for trainCtcPars --max_epochs.
max_nondecreasing_epochsNoEarly stopping patience (default: 20). Shortcut for trainCtcPars --max_nondecreasing_epochs.
learning_rateNoLearning rate (default: 3.0E-4). Shortcut for trainCtcPars --learning_rate.
batch_sizeNoBatch size (default: 24). Shortcut for trainCtcPars --batch_size.
noTrainingDefaultsNoIf true, do NOT apply UI-default training parameters. The server will use its own defaults (which differ from the UI and may produce worse models).
Behavior4/5

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

Annotations show readOnlyHint=false and openWorldHint=true. The description adds significant behavioral context: that by default it sends UI defaults, and without them the server uses different preprocessing leading to worse models. It also explains that parameters are merged with UI defaults. This goes beyond the annotations, though it could mention job creation or cost implications.

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 concise (three sentences) and front-loaded with the main purpose. It packs critical information about defaults and warnings without excessive verbosity. However, the technical details could be slightly overwhelming for an agent, but overall it's efficient.

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 high parameter count (24) and complex default behavior, the description covers the key behavioral aspects: defaults, merging, and the noTrainingDefaults option. It does not explain how to use the result (e.g., job completion, model ID retrieval) but the tool name and context make the purpose clear. It is reasonably complete for an agent to use correctly.

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 100%, so each parameter already has a description. The tool description adds value by explaining the merging behavior for textFeatsCfg, createModelPars, and trainCtcPars, and the shortcut parameters (max_epochs, etc.). It clarifies the role of noTrainingDefaults, which is not detailed in the schema. This adds meaning beyond the 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?

The description clearly states 'Start PyLaia HTR model training for a collection'. It specifies the resource (PyLaia model) and the action (training). The mention of UI defaults distinguishes it from siblings like transkribus_recog_train_htr_citlab, and the tool name itself is very specific.

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?

The description explains when to use this tool (training PyLaia models) and the impact of the noTrainingDefaults flag. It warns that server defaults produce worse models, providing a clear context. However, it does not explicitly compare with other training tools (e.g., transkribus_recog_train_htr_citlab) or specify when not to use it.

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/lazyants/transkribus-mcp-server'

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