transkribus_page_get_metadataRetrieve metadata for a specific page in a Transkribus document. Provide collection ID, document ID, and page number to get page-level details.
Get metadata for a specific 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 declare the tool as read-only, non-destructive, idempotent, and open-world. The description adds no behavioral context beyond what annotations provide, such as what metadata is included or any limitations.
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?
The description is a single sentence of 6 words, highly concise and front-loaded. Every word is necessary to convey the core purpose, with no redundancy.
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?
Given the lack of an output schema and the tool's simple nature, the description minimally conveys the function. However, it does not describe the kind of metadata returned (e.g., image dimensions, OCR status), which would aid completeness. Annotations partially compensate but do not cover return value details.
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?
The input schema has 100% coverage with descriptions for each parameter (collId, id, page). The description does not add additional meaning or examples beyond the schema, so it meets the baseline.
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 tool retrieves metadata for a specific page, using a verb ('Get') and resource ('metadata for a specific page'). It distinguishes from siblings like transkribus_page_get and transkribus_doc_get_metadata by the focus on page-level metadata, but does not explicitly differentiate among similar page-related tools.
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?
The description provides no guidance on when to use this tool versus alternatives such as transkribus_doc_get_metadata or transkribus_coll_get_metadata. It does not mention prerequisites, context, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.