Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Run Layout Analysis

transkribus_la_analyze

Run layout analysis on document pages to identify text blocks, lines, and words. Specify collection and document IDs, select page ranges, and enable segmentation options to structure scanned pages for further processing.

Instructions

Run layout analysis on document pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docIdYesDocument ID
pagesNoPage range (e.g. "1-5" or "1,3,5")
collIdYesCollection ID
creditsNoCredits parameter
jobImplNoJob implementation class
doLineSegNoPerform line segmentation
doWordSegNoPerform word segmentation
doBlockSegNoPerform block segmentation
doBaselineToPolygonNoConvert baselines to polygons
doPolygonToBaselineNoConvert polygons to baselines

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 indicate it is a mutation (readOnlyHint=false), but the description does not disclose details like job creation, return values, or side effects. The description adds minimal value beyond annotations.

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, concise but lacks structure and is overly minimal. Every word is earned but insufficient for a complex tool.

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 tool's complexity (10 parameters, no output schema, job execution), the description omits critical context like return type, parameter usage, and job lifecycle.

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 baseline is 3. The description adds no additional parameter meaning beyond what the schema already provides.

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 clearly states the action 'run' and the resource 'layout analysis on document pages'. It is specific but does not differentiate from siblings like transkribus_la_analyze_advanced.

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 versus alternatives, such as the advanced version or cost-related tools. No prerequisites or context provided.

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