Skip to main content
Glama
Sign In
lexware-mcp-server

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Download File

lexware_download_file
Read-onlyIdempotent

Download a Lexware file as base64-encoded content, choosing PDF by default or XML for an available e-invoice original.

Instructions

Download a file from Lexware as base64-encoded content. Choose pdf (default) or xml for an available e-invoice XML original.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "lexware_download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFile UUID
formatNoRepresentation to request: "pdf" (default) or "xml" for an available e-invoice XML file; XML embedded in a PDF cannot be retrieved separately.pdf

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.3.0
    • addedInput schema / properties / format
      Added value: +{
+  "default": "pdf",
+  "description": "Representation to request: \"pdf\" (default) or \"xml\" for an available e-invoice XML file; XML embedded in a PDF cannot be retrieved separately.",
+  "enum": [
+    "pdf",
+    "xml"
+  ],
+  "type": "string"
+}
  2. First observedv3.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description usefully adds that content is returned base64-encoded and that XML embedded in a PDF cannot be retrieved separately, but it does not cover error behavior, availability limits, or file-status prerequisites.

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?

Two tight sentences with no waste. The core action and its return encoding are front-loaded, and the format choice follows immediately, which is the right order for a two-parameter tool.

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

Completeness3/5

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

With no output schema, the description correctly covers the return shape (base64 content). It is adequate for calling the tool, but for a generic download sitting beside a dozen document-specific download siblings, it should clarify scope (any file id vs. typed document files) to be fully complete.

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 description coverage is 100%, so both parameters are fully documented in the schema itself, including the pdf default and the e-invoice XML caveat. The description's mention of pdf/xml largely restates the schema, adding no syntax or meaning beyond it; baseline 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?

States a specific verb and resource ('Download a file from Lexware') and discloses the return encoding (base64), so the operation is unambiguous. However, it does not distinguish this generic file download from the many sibling tools like lexware_download_invoice_file or lexware_download_quotation_file, so an agent cannot tell from the description alone which one to reach for.

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?

The description says nothing about when to use this generic download versus the document-specific download siblings, nor any prerequisite (e.g. that the id must reference an existing file). The only guidance offered is on the format parameter, not on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools