transkribus_search_replaceFind and replace a search term with a replacement across Transkribus documents, optionally scoped to a specific document or collection.
Search for a term and replace it across documents.
| Name | Required | Description | Default |
|---|---|---|---|
| docId | No | Limit to a specific document ID | |
| collId | No | Limit to a specific collection ID | |
| searchTerm | Yes | Term to search for | |
| replaceTerm | Yes | Replacement term |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate mutation (readOnlyHint=false) but description adds no detail about scope, reversibility, or side effects beyond 'replace across documents'. For a mutation tool, more behavioral context is expected.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence conveys core purpose efficiently, though additional details could be incorporated without harming conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Description lacks explanation of scope (e.g., which documents are affected) and return value. With no output schema, the agent needs hints about what the tool returns.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with parameter descriptions. Description adds no extra semantics beyond what is already in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states search and replace action across documents. However, it does not differentiate from sibling tool transkribus_search_replace_in_collection, which likely has similar purpose but scoped to collections.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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_search_replace_in_collection). No prerequisites or limitations mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.