transkribus_model_add_collection_by_idAdd a collection to an HTR model by specifying model ID and collection ID, linking documents for training or recognition.
Add a collection to a model by model ID and collection ID.
| Name | Required | Description | Default |
|---|---|---|---|
| collId | Yes | Collection ID | |
| modelId | Yes | Model/HTR ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (non-readonly, not destructive, not idempotent), the description adds no behavioral context such as whether the tool checks existence, returns anything, or overwrites existing associations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, no unnecessary words. Efficiently conveys the core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with two integer parameters and no output schema, the description is minimally complete but lacks context on side effects, error conditions, or reversibility (e.g., sibling removal tool exists).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and descriptions are provided for both parameters. The tool description does not add further meaning beyond restating parameter names, so baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Add a collection to a model') and the identifiers used (model ID and collection ID). It distinguishes from removal tools but does not differentiate from the sibling 'transkribus_model_add_collection' which may have similar purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'transkribus_model_add_collection'. No prerequisites or context for usage provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.