transkribus_page_count_transcriptsCount the transcripts for a page in a Transkribus document by providing collection ID, document ID, and page number. Get the total number of available transcripts for that page.
Get the number of transcripts for a page.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Document ID | |
| page | Yes | Page number | |
| collId | Yes | Collection ID |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering the safety profile. The description adds no extra behavioral details (e.g., return type or side effects), but the existing annotations moderate the need for more transparency.
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?
Description is a single, efficient sentence with no wasted words. It is appropriately concise for a simple count operation.
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?
While the tool is simple and annotations provide good context, the description does not specify the return type (e.g., integer count) or any additional details that might be helpful. It is adequate but leaves minor ambiguity.
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?
Input schema covers all parameters (collId, id, page) with descriptions, achieving 100% coverage. The description adds no additional meaning beyond the schema, so it meets the baseline without enrichment.
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 the verb 'Get' and the resource 'the number of transcripts for a page', which is specific and distinct from sibling tools like transkribus_page_list_transcripts (lists transcripts) and transkribus_page_get_transcript (gets a specific transcript).
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 such as transkribus_page_list_transcripts or transkribus_page_get_transcript. The description does not provide context for when a count is appropriate over listing or retrieving a transcript.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.