Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants

Download File

lexware_download_file
Read-onlyIdempotent

Retrieve a file from Lexware by providing its UUID. Returns the file content base64-encoded.

Instructions

Download a file from Lexware. Returns the file as base64-encoded content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFile UUID
Behavior3/5

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

Annotations already declare the tool as read-only, non-destructive, idempotent, and open-world. The description adds that it returns base64 content, which is helpful but does not disclose other behavioral traits like file size limits or error handling.

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

Conciseness5/5

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

The description is extremely concise at two sentences, front-loading the action and output format without any fluff. Every word is meaningful.

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 one-parameter tool, the description provides essential information (base64 output) and sufficient context for invocation. However, it could be more complete by mentioning that this tool is for generic file downloads not covered by specific document-type download tools.

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?

The input schema has 100% coverage with a description of the 'id' parameter as 'File UUID'. The tool description adds no additional meaning beyond that, so the baseline score of 3 applies.

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 ('Download'), the resource ('a file from Lexware'), and the output format ('base64-encoded content'). However, it does not differentiate this generic download tool from the many sibling tools for specific document types (e.g., lexware_download_invoice_file), which could cause confusion about when to use this tool.

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 is provided on when to use this tool versus the specific download tools for invoices, credit notes, etc. The agent is left to infer based on the naming convention, which is not explicitly explained.

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/lexware-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server