Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

Get Model Field Parameters

transkribus_model_get_field_params
Read-onlyIdempotent

Retrieve field parameters for a Transkribus model by model family and ID to inspect its configuration details before running recognition or extraction tasks.

Instructions

Get the field parameters 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_field_params"
  }
}

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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety behavior is covered. Beyond that the description adds nothing: it does not say what 'field parameters' contain, whether any permission is needed, or how the result relates to other model endpoints.

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 or redundancy, and the type/ID scoping is front-loaded. It is efficient, though the brevity comes at the cost of substance rather than being a structural flaw.

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 no output schema and no explanation of what field parameters are or what shape they take, an agent cannot anticipate the response or judge whether this tool fits its need. For a two-required-parameter lookup tool it should at minimum define the returned concept and point to the relevant sibling.

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% and the schema itself supplies the meaningful detail, including the model family values (text, layout, smartextract) and the positive-integer constraint on id. The description merely restates that a type and ID are required, adding no syntax or format meaning beyond the schema, so 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?

States a specific verb (get) and resource (field parameters) scoped by type and ID, so the operation is identifiable. But 'field parameters' is never defined, and it does nothing to separate itself from siblings like transkribus_model_get_details or transkribus_model_get_by_type, which plausibly return overlapping model data.

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 when-to-use guidance at all: no prerequisites, no indication of when this is preferred over model_get, model_get_by_type or model_get_details, and no exclusions. The agent must infer selection purely 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