Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

Get Document Pages

transkribus_doc_get_pages
Read-onlyIdempotent

Retrieve all pages of a document with filters like page range, status, and recognition type to narrow down results.

Instructions

Get all pages for a document.

Input Schema

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

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral details such as pagination behavior, response format, or how filters affect results.

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 description is a single sentence, which is concise and front-loaded. However, it lacks substance and could benefit from more detail to be truly useful. It is minimally adequate but not well-structured.

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 the complexity of 22 parameters and no output schema, the description fails to provide essential context about return values, filtering semantics, or how this tool differs from similar sibling tools like transkribus_doc_list_pages.

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 coverage is 100% with descriptions for all 22 parameters. The tool description does not add any additional meaning beyond what the schema provides, so it meets the baseline but does not elevate understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get all pages for a document,' which is a clear verb+resource pair. However, the input schema includes many filter parameters (pages, status, etc.), implying the tool can retrieve a subset, not just all pages. This mismatch makes the purpose somewhat vague and potentially misleading.

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?

No guidance is provided on when to use this tool versus alternatives like transkribus_doc_list_pages or transkribus_doc_get_page_ids. There is no mention of prerequisites or context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazyants/transkribus-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server