Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

Get Document Pages

transkribus_doc_get_pages
Read-onlyIdempotent

Fetch all pages for a document using collection and document IDs, with optional filters for status, page range, model, and file name.

Instructions

Get all pages for a document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDocument ID
indexNoStart index (0-based)
pagesNoPage range filter
collIdYesCollection ID
statusNoFilter by status
labelIdNoFilter by label ID
modelIdNoFilter by model ID
nValuesNoNumber of results (-1 for all)
clientIdNoFilter by client ID
ctStatusNoFilter by CT status
fileNameNoFilter by file name
modelNameNoFilter by model name
modelTypeNoFilter by model type
clientNameNoFilter by client name
sortColumnNoColumn to sort by
hideOnSitesNoFilter by hide on sites flag
modelUserIdNoFilter by model user ID
modelUserNameNoFilter by model user name
pagingWrapperNoUse paging wrapper
sortDirectionNoSort direction: asc or desc
recognitionTypeNoFilter by recognition type
skipPagesWithMissingStatusNoSkip pages with missing status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.0.0
    • changedInput schema / properties / index / description
      Previous value: -"Start index"New value: +"Start index (0-based)"
    • changedInput schema / properties / index / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / nValues / description
      Previous value: -"Number of values (-1 for all)"New value: +"Number of results (-1 for all)"
    • changedInput schema / properties / sortDirection / description
      Previous value: -"Sort direction (asc/desc)"New value: +"Sort direction: asc or desc"
  2. First observedv2.1.1

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond that, such as pagination defaults, filter interaction, or how the tool handles large documents.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-sentence description is front-loaded and free of filler. For a 22-parameter tool, though, it is arguably too terse to be appropriately sized, leaving important behavioral context unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 22 parameters, two required IDs, filter and pagination options, and no output schema, a single sentence is not complete enough. The description omits return shape, pagination behavior, filter semantics, and its relationship to similar page-listing siblings.

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%, so all 22 parameters are documented in the input schema. The description does not add any parameter meaning or clarify the filter/paging surface, so the baseline score of 3 applies.

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 names a specific verb (Get) and resource (pages for a document), making the core purpose clear. However, it does not distinguish this tool from close siblings such as transkribus_doc_list_pages or transkribus_doc_get_page_ids, so no sibling differentiation is present.

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?

The description gives no indication of when to use this tool versus alternatives like transkribus_doc_list_pages or transkribus_page_get, nor does it mention prerequisites such as required collection/document context. Usage is left entirely to inference.

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