Skip to main content
Glama
Sign In
buchpilot-mcp

buchpilot-mcp

by makririch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_vouchers

Retrieve vouchers with optional filters by type and limit. Filter purchase invoices, credit notes, or any vouchers to manage accounting records.

Instructions

Listet Belege auf mit optionalen Filtern. Lists vouchers with optional filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
typeNoNach Typ filtern
limitNoMaximale Anzahl
backendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as pagination, ordering, or side effects. For a listing tool, this is a significant gap.

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?

Two short, front-loaded sentences with minimal redundancy. Could be merged into one, but not overly verbose.

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?

Missing details on result format, pagination, error handling, and ordering. Compared to sibling list tools, this description is incomplete for a full understanding.

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 covers 67% of parameters with descriptions; the tool description adds no extra meaning beyond 'optional filters'. The backend parameter lacks description, but schema coverage is adequate for baseline.

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?

The description clearly states the verb 'list' and the resource 'vouchers', distinguishing it from 'get_voucher' which retrieves a single voucher. The bilingual phrasing reinforces the action.

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 tool versus siblings like 'list_contacts' or 'list_invoices'. No mention of when not to use it or prerequisites.

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