Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants

Keyword Search

transkribus_search_keyword
Read-onlyIdempotent

Search for documents in Transkribus collections by keyword. Filter results by collection ID, probability threshold, fuzzy matching, and more.

Instructions

Search for documents matching a keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword search query
collIdNoLimit search to a specific collection ID
startNoStart offset
rowsNoNumber of results
probLNoLower probability threshold
probHNoUpper probability threshold
filterNoFilter string
fuzzyNoFuzzy matching level
sortingNoSorting mode
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral context such as pagination, result format, or rate limits. For a tool with many parameters, more transparency would be helpful.

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?

The description is a single sentence with no wasted words, making it concise and front-loaded. However, it might be too terse given the tool's complexity (9 parameters, multiple siblings).

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?

For a tool with 9 parameters and no output schema, the description is incomplete. It does not explain how keyword search works, how parameters interact, or what the response looks like. The annotations cover safety but not usage details.

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 the schema already documents all parameters. The description does not add any additional meaning or context for the parameters, which is acceptable given high coverage.

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 tool searches for documents by keyword, with a specific verb and resource. However, it does not explicitly differentiate from sibling tools like transkribus_search_fulltext or transkribus_search_tags, which is a minor gap.

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, no prerequisites or context for use. The single sentence provides no usage direction beyond the basic purpose.

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