Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

Add Collection to Model

transkribus_model_add_collection

Add a collection to a Transkribus model by specifying the model family, model ID, and collection ID. Use it to link collections to text, layout, or smartextract models.

Instructions

Add a collection to a model by type and model 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>",
      "modelId": "<modelId>",
      "collId": "<collId>"
    },
    "name": "transkribus_model_add_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesModel family: text, layout or smartextract
collIdYesCollection ID to add
modelIdYesModel/HTR ID

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

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=true, so safety is covered. The description adds nothing beyond that: it does not say what happens if the collection is already attached, whether an error or no-op occurs, whether permissions on the model are required, or that the model family must be one of text/layout/smartextract.

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?

One short front-loaded sentence with no filler or redundancy. It is efficient rather than verbose, though its brevity borders on under-specification.

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 three-parameter mutation with full schema coverage and meaningful annotations, the essentials are covered by structured fields, and no output schema is needed. Missing is any statement of duplicate-add behavior and an explicit routing rule against the by_id sibling, which matter for a non-idempotent write.

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 three parameters (type, modelId, collId) are already documented in the schema, including the model-family values. The description only echoes type and modelId and omits collId, adding no syntax or format meaning beyond the schema; baseline 3 applies.

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?

The description states a specific verb and resource ("Add a collection to a model") and adds the keying phrase "by type and model ID", which implicitly separates it from the sibling transkribus_model_add_collection_by_id. It is clear what the tool does, though the sibling distinction is hinted rather than spelled out.

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

Usage Guidelines3/5

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

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. The phrase "by type and model ID" weakly signals the choice against the _by_id variant, but the agent must infer that routing rule itself.

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