Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

Get Validation Data

transkribus_model_get_validation_data
Read-onlyIdempotent

Retrieve validation data for a specific model by model type and ID, with optional start index and result count for paginated inspection.

Instructions

Get the validation data for a model by type and ID.

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_validation_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesResource ID
typeYesModel family: text, layout or smartextract
indexNoStart index (0-based)
nValuesNoNumber of results (-1 for all)

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. Changed5 schema fields changedv4.0.0
    • addedInput schema / properties / index / default
      Added value: +0
    • changedInput schema / properties / index / description
      Previous value: -"Start index"New value: +"Start index (0-based)"
    • changedInput schema / properties / index / minimum
      Previous value: --9007199254740991New value: +0
    • addedInput schema / properties / nValues / default
      Added value: +-1
    • changedInput schema / properties / nValues / description
      Previous value: -"Number of values"New value: +"Number of results (-1 for all)"
  3. Changed1 schema field changedv3.0.0
    • addedInput schema / properties / type / pattern
      Added value: +"^[^/\\s]+$"
  4. First observedv2.1.1

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. Beyond the annotations, the description adds nothing: it does not explain whether the data is precomputed or computed on demand, how the pagination parameters (index, nValues) affect results, or what happens with an unknown model ID. For an open-world read tool with no output schema, this is thin.

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 front-loaded sentence with zero filler or redundancy. It is efficient, though its brevity borders on under-specification rather than being a model of concision.

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

Completeness2/5

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

With four parameters, no output schema, and ambiguous return contents, the description should disclose what the validation data looks like and how pagination behaves. Instead it leaves an agent guessing, which is inadequate for the tool's complexity.

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%, so all four parameters (id, type, index, nValues) are already documented, including the model-family values and nValues=-1 for all. The description merely repeats "by type and ID" and adds no format, ordering, or constraint detail beyond the schema; baseline 3 applies.

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

Purpose3/5

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

The description states a verb ("Get") and a resource ("validation data for a model") and adds the lookup keys (type and ID), which is more than a bare restatement of the title. However, it never clarifies what "validation data" actually contains, and it does not distinguish this tool from near-identical siblings such as transkribus_model_get_validation_data_docs or _stats, so an agent cannot tell them apart from the description alone.

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?

There is no guidance on when to use this tool versus the many sibling variants (docs, stats, doc-scoped validation data, train-data counterparts). The reader is left to infer the selection criteria entirely from tool names.

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