Skip to main content
Glama
sevdesk-mcp

sevdesk-mcp

by joosthel

Upload a receipt file (inline)

sevdesk_upload_voucher_file_content

Upload base64-encoded receipt files to sevDesk temporary voucher storage and return a fileName token for creating a voucher; supports PDF, PNG, JPG, XML up to 10 MB.

Instructions

Upload a receipt sent inline as base64 (e.g. an e-mail attachment) to sevDesk's temporary voucher storage — for hosted clients that cannot use sevdesk_upload_voucher_file's local path. Returns fileName, the token sevdesk_create_voucher attaches to a new voucher. PDF, PNG, JPG and XML (XRechnung / ZUGFeRD e-invoice) only, checked by content and not only the name, at most 10 MB. Accepts standard and URL-safe base64 and data: URLs. Creates no voucher by itself. ⚠️ This tool can change data in sevDesk.

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": {
      "fileName": "<fileName>",
      "base64Content": "<base64Content>"
    },
    "name": "sevdesk_upload_voucher_file_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoCheck the file without uploading it.
fileNameYesOriginal file name with extension .pdf, .png, .jpg, .jpeg or .xml.
base64ContentYesThe file content, base64 encoded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations it discloses validation behavior (type checked by content, not just extension), a hard size limit (10 MB), accepted input encodings (standard, URL-safe base64 and data: URLs), the temporary nature of the storage, and the return value shape (fileName token). The mutation warning complements readOnlyHint=false with concrete consequences rather than merely restating it.

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?

Purpose and the sibling distinction are front-loaded, followed by return value, constraints, and the mutation warning in descending order of importance. Every clause carries distinct actionable information; there is no restatement of the tool name or schema fields.

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

Completeness5/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 still explains what comes back (fileName token) and what does not happen (no voucher created). For a three-parameter upload tool with full annotation coverage, nothing an agent needs to call it correctly or handle the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by clarifying that base64Content accepts URL-safe base64 and data: URLs, which the schema does not say, and by tying the returned fileName token to sevdesk_create_voucher. It does not explain dryRun semantics, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Upload a receipt sent inline as base64 ... to sevDesk's temporary voucher storage") and immediately distinguishes itself from sevdesk_upload_voucher_file by naming the constraint that selects it (hosted clients that cannot use a local path). An agent can pick between the two upload tools without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use condition (hosted clients without local path access), names the sibling alternative for the other case, and states the downstream step by naming sevdesk_create_voucher as the consumer of the returned token. It also excludes a misreading with "Creates no voucher by itself."

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