transkribus_server_available_filesRetrieve available client files hosted on the server, optionally filtering by release type. Check which files are ready for download or deployment.
List available client files on the server.
| Name | Required | Description | Default |
|---|---|---|---|
| isRelease | No | Filter release files |
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, indicating a safe, read-only operation. The description adds no additional behavioral details such as pagination, response format, or filtering behavior beyond the single parameter.
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?
The description is a single, clear sentence with no unnecessary words. It is appropriately front-loaded with the action and resource. However, it could benefit from a bit more context without sacrificing 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?
For a list tool with no output schema and only one optional parameter, the description is overly sparse. It does not explain what 'client files' are, how results are returned, or how the 'isRelease' filter affects the output. Given the complex ecosystem of sibling tools, this lack of context impairs correct selection and invocation.
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?
The input schema covers 100% of parameters (only 'isRelease' with description and default). The description does not add any extra meaning or usage context for the parameter, so it does not compensate beyond the schema's baseline. A score of 3 is appropriate.
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?
The description clearly states the action ('List') and the resource ('available client files on the server'). It effectively distinguishes from sibling tools that list other types of files or resources, such as transkribus_file_list_files or transkribus_doc_get_image_names.
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?
The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, limitations, or contextual scenarios. With numerous sibling tools for listing files, this omission reduces usability.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.