Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

Get Training Data Statistics

transkribus_model_get_train_data_stats
Read-onlyIdempotent

Retrieves training data statistics for a Transkribus model by model family and resource ID, helping assess dataset size and composition before training or evaluation.

Instructions

Get statistics about the training data for a model.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "transkribus_model_get_train_data_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource ID
typeYesModel family: text, layout or smartextract

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.2.0
    • changedInput schema / properties / type / description
      Previous value: -"Model type (e.g. htr, la, ocr)"New value: +"Model family: text, layout or smartextract"
  2. Changed1 schema field changedv3.0.0
    • addedInput schema / properties / type / pattern
      Added value: +"^[^/\\s]+$"
  3. First observedv2.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds nothing beyond them: it does not say what the statistics contain, whether an untrained model errors or returns empty, or how expensive/large the response is.

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?

A single short sentence with no filler and the verb-resource pair front-loaded. It is efficient, though its brevity edges into under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage and complete read-only annotations, the minimum needed to call it is present. However, with no output schema, the description should indicate what kind of statistics come back and whether the model must be trained, which it omits.

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 'id' documented as Resource ID and 'type' documented as model family (text, layout, smartextract), so the schema carries parameter meaning. The description mentions only 'model' generically and adds no constraints or format notes beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get statistics about the training data for a model'), which is clear enough to distinguish from the validation-data sibling by the word 'training'. It does not name that sibling explicitly, so the differentiation relies on the agent noticing the wording.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus transkribus_model_get_train_data, transkribus_model_get_train_data_docs, or transkribus_model_get_validation_data_stats. No prerequisites are mentioned (e.g., whether the model must exist or be in a training state).

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