Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

Remove Collection from Model

transkribus_model_remove_collection
DestructiveIdempotent

Removes a collection from a specified model using model type, model ID, and collection ID, so you can detach collections from text, layout, or smartextract models.

Instructions

Remove a collection from a model by type, model ID, and collection 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_remove_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesModel family: text, layout or smartextract
collIdYesCollection ID
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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond that: it does not say whether the collection itself is preserved (only the link removed), whether removal is reversible, what error occurs if the association does not exist, or whether a model-family mismatch is rejected.

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 and the required identifiers named up front. It is efficient, but the terseness is arguably under-specification rather than disciplined conciseness given the destructive nature of the call.

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?

For a destructive, open-world mutation with three required parameters and no output schema, the description should explain the effect on the underlying collection and the failure modes. It omits both, and also fails to differentiate the tool from its _by_id sibling, so an agent cannot confidently invoke it without opening the schema and guessing.

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% — 'type' is documented as the model family (text, layout, smartextract), 'collId' as collection ID, 'modelId' as model/HTR ID — and the description merely restates these roles. No format, constraint, or cross-parameter relationship is added beyond the schema, so the baseline of 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?

States a specific verb and resource ('Remove a collection from a model') and enumerates the three identifiers that scope the operation, so the agent knows it is an association-removal action. It does not, however, distinguish itself from the near-identically named sibling transkribus_model_remove_collection_by_id, leaving the agent to guess which of the two to pick.

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 when-to-use guidance, no prerequisite (e.g. the collection/model must exist, correct model family), and no exclusion or routing to alternatives. With siblings like transkribus_model_remove_collection_by_id and transkribus_model_add_collection present, the absence of any disambiguation is a meaningful gap, not just an omission.

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