Skip to main content
Glama
transkribus-mcp-server

transkribus-mcp-server

by lazyants

List Model Collections

transkribus_model_list_collections
Read-onlyIdempotent

Lists collections linked to a model by its family and ID, so you can see which collections a text, layout, or smartextract model is used in.

Instructions

List collections associated with 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_list_collections"
  }
}

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, open-world behavior, so the safety profile is covered by structured data. The description adds nothing beyond it: no note on pagination, result size, whether an empty list or error occurs for unknown ids, or what a "collection" contains.

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 no filler or repetition. Its brevity is close to under-specification rather than waste, so it is efficient but thin.

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 no output schema, the description is minimally sufficient to invoke it correctly. It leaves gaps around return shape and the distinction from the by_id sibling, which matters given the size of the surrounding catalog.

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 both parameters documented (id as resource ID, type as model family), so the schema does the semantic work. The phrase "by type and ID" merely restates the required parameters and adds no format, range, or edge-case detail.

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 gives a specific verb and resource ("List collections") plus the scoping ("associated with a model by type and ID"), so an agent knows it is a read of collection memberships for a given model. It does not, however, distinguish this from the near-identical sibling "transkribus_model_list_collections_by_id", which an agent would have to disambiguate on its own.

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 or when-not-to-use guidance, and no explicit routing to alternatives despite a crowded sibling set (by_id, doc_, recog_, coll_ variants). The only usage clue is the implied "given a model type and id", which the schema already enforces.

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