Skip to main content
Glama
Sign In
buchpilot-mcp

buchpilot-mcp

by makririch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_invoice_pdf

Download an invoice as a base64-encoded PDF by providing the invoice ID. Retrieve invoice documents directly for processing or storage.

Instructions

Laedt eine Rechnung als PDF herunter (Base64-kodiert). Downloads an invoice as PDF (base64-encoded).

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": "get_invoice_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRechnungs-ID
backendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It discloses the return format (base64-encoded PDF) but lacks details on authorization, side effects, 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.

Conciseness4/5

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

Description is short and clear, using bilingual text. While efficient, the structure could be improved with a single language or bullet points.

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?

Adequate for a simple download tool: states action and format. Lacks instruction on how to use the base64 output (e.g., decode) and error scenarios.

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?

Schema describes 'id' as 'Rechnungs-ID' but 'backend' lacks description. The description adds no parameter-level meaning beyond the schema, leaving the 'backend' param undocumented.

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?

Description clearly states the action (download), resource (invoice PDF), and format (base64-encoded) in both German and English, distinguishing it from sibling tools that return JSON data.

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

Usage Guidelines3/5

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

Implied usage: use when needing a PDF of an invoice. No explicit when-not or alternatives provided, but the purpose is clear from the name and description.

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