Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

Assign Plaintext to Page

transkribus_page_assign_plaintext
Idempotent

Assign plain text to a document page as a new transcript, requiring collection ID, document ID, page number, and text.

Instructions

Assign plain text content to a page as a new transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collIdYesCollection ID
idYesDocument ID
pageYesPage number
textYesPlain text content to assign
statusNoTranscript status
noteNoNote for the transcript
parentNoParent transcript ID
nrIsPageIdNoTreat page nr as page ID
toolNameNoTool name that created the transcript
useExistingLayoutNoUse existing layout
Behavior2/5

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

Says 'assign as a new transcript' contradicts idempotentHint=true (creating a new transcript each call is not idempotent). No other behavioral traits disclosed.

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

Conciseness5/5

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

Single sentence with clear action and no wasted words. Front-loaded with purpose.

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?

With 10 parameters, no output schema, and an annotation contradiction, the description lacks important context about behavior (e.g., idempotency, relationship to existing transcripts).

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%, so description adds no new meaning. Baseline 3 is appropriate.

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

Purpose5/5

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

Description clearly states action (assign), resource (page), and content (plain text). Distinguishes from siblings like transkribus_page_get_plaintext and transkribus_page_post_transcript.

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 on when to use this tool vs alternatives (e.g., transkribus_page_post_transcript). No prerequisites or exclusions mentioned.

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