sevdesk MCP Server

get_invoice_pdf

Retrieve the PDF of any invoice as a base64 encoded string by providing its invoice ID.

Instructions

Get the PDF of an invoice as base64 encoded string

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": {
      "invoiceId": "<invoiceId>"
    },
    "name": "get_invoice_pdf"
  }
}

Input Schema

Name	Required	Description
`download`	No
`invoiceId`	Yes	The ID of the invoice
`preventSendBy`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, and description only mentions output format without disclosing side effects, error handling, or permissions needed for PDF retrieval.

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

Conciseness4/5

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

Single sentence, front-loaded with key action and output format, but omits necessary parameter details.

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

Completeness2/5

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

No output schema, and description fails to fully explain parameters (2 of 3 undocumented), leaving the agent with incomplete context for invocation.

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

Parameters2/5

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

Only invoiceId is described in schema (33% coverage); description does not explain download or preventSendBy params, adding no value beyond schema.

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?

Specifically states 'Get the PDF of an invoice' and notes the output format (base64 encoded string), distinguishing it from siblings like get_invoice which likely returns JSON.

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 on when to use this vs alternatives, no prerequisites or exclusion criteria provided.

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