transkribus_model_list_collections_by_idRetrieve collections linked to a specific model by providing its ID. Use this to identify which collections use a given HTR model.
List collections associated with a model by its ID.
| Name | Required | Description | Default |
|---|---|---|---|
| modelId | Yes | Model/HTR ID | |
| transcriptIds | No | Include transcript IDs |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, but description adds no additional behavioral traits such as pagination, sorting, error handling, or what 'collections' includes. Minimal added value.
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?
Single sentence, no unnecessary words. Could be slightly more informative but is efficient.
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 list tool with two parameters and annotations covering safety, it is adequate. However, lacking output schema, it would benefit from saying what the response contains (e.g., list of collection IDs/names).
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% with descriptions for both parameters. The description does not add meaning beyond the schema, e.g., explaining how 'transcriptIds' affects the output. Baseline 3 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?
Description clearly states verb 'List' and resource 'collections associated with a model by its ID'. The name itself is descriptive, but does not explicitly differentiate from siblings like 'transkribus_model_list_collections' which may have different parameters.
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 vs alternatives such as 'transkribus_model_list_collections' or 'transkribus_model_get'. No mention of prerequisites or when 'transcriptIds' should be used.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.