Skip to main content
Glama
Sign In
sevdesk-mcp

sevdesk-mcp

by joosthel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List outgoing invoices

sevdesk_list_invoices
Read-only

Retrieve issued invoices with customer, amounts, status, and dates; filter by date range and row limit for read-only reporting and reconciliation.

Instructions

List invoices you issued, with number, customer, sums, status and dates. Read-only.

Input Schema

NameRequiredDescriptionDefault
toNoEnd date.
fromNoStart date.
limitNoMaximum rows (default 200).
maxItemsNoFetch cap: how many records are read from sevDesk before filtering (default 2000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / maxItems
      Added value: +{
+  "description": "Fetch cap: how many records are read from sevDesk before filtering (default 2000).",
+  "maximum": 20000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only.' adds nothing. The one genuinely useful disclosure is the shape of returned records (number, customer, sums, status, dates), which substitutes for the missing output schema, but nothing is said about pagination or how the fetch cap affects completeness.

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?

One front-loaded sentence plus a two-word tag; no filler. The trailing 'Read-only.' is redundant with the annotations and slightly dilutes conciseness.

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?

For a 4-param filter tool with no output schema, listing returned fields is a meaningful contribution. Still absent is any statement about result volume behavior (limit default 200 vs maxItems default 2000) or ordering, which an agent needs to interpret results correctly.

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 baseline 3 applies. The description does not discuss from/to, limit, or maxItems semantics—in particular the distinction between the row limit and the fetch cap—leaving that entirely to the schema text.

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?

Specific verb+resource: 'List invoices you issued' with an enumeration of returned fields. 'Issued' implicitly separates it from vouchers/transactions siblings, but there is no explicit contrast with sevdesk_list_vouchers or sevdesk_summarize, so differentiation relies on inference.

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?

Usage is implied by the name and the field list (fetch issued invoices), and 'Read-only' signals a safe read path. However, there is no explicit when-to-use guidance, no mention of when to prefer sevdesk_list_vouchers/sevdesk_summarize, and no note on when date filters are needed.

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