Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

List Crowdsourcing Projects

transkribus_crowdsource_list
Read-onlyIdempotent

List available crowdsourcing projects from Transkribus, with pagination and sorting parameters.

Instructions

List available crowdsourcing projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexNoStart index (0-based)
nValuesNoNumber of results (-1 for all)
sortColumnNoColumn to sort by
sortDirectionNoSort direction: asc or desc
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds no additional behavioral context beyond what annotations provide, such as pagination or result format.

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

Conciseness4/5

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

Description is a single sentence, concise and direct. While it could include a bit more detail, it avoids unnecessary verbosity.

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

Completeness4/5

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

For a simple list operation with comprehensive annotations and fully described parameters, the description is adequate. It clearly states what it does, though it does not mention the return format or any result limits.

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?

Input schema has 100% description coverage for all 4 parameters. The description does not add any extra meaning beyond what is already in the schema, so baseline score of 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 ('List') and resource ('crowdsourcing projects'). It is specific and distinguishes from sibling tools like transkribus_crowdsource_get_details or transkribus_crowdsource_subscribe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. Usage is implied (when you need a list), but no exclusions or alternative tool mentions are provided.

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