Skip to main content
Glama
sevdesk-mcp

sevdesk-mcp

by joosthel

List sevDesk API operations

sevdesk_list_operations
Read-only

Search the sevDesk API catalogue to find operationIds for endpoints lacking dedicated tools, filtering by resource tag, read/write effect, or free-text query.

Instructions

Search the sevDesk API catalogue (154 operations, API 2.0.0) for the operationId of anything not covered by a dedicated tool. Available tags: AccountingContact, Basics, CheckAccount, CheckAccountTransaction, CommunicationWay, Contact, ContactAddress, ContactField, CreditNote, CreditNotePos, Export, Invoice, InvoicePos, Layout, Order, OrderPos, Part, PrivateTransactionRule, Report, Tag, Voucher, VoucherPos.

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

Input Schema

NameRequiredDescriptionDefault
tagNoRestrict to one resource tag, e.g. 'Voucher' or 'Invoice'.
kindNoFilter by effect: read (GET), write (POST/PUT/DELETE), or all.
limitNoMaximum results (default 60).
queryNoFree-text search over operationId, path, tags and summary, e.g. 'voucher pdf'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / tag / enum
      Previous value: -[
      -  "AccountingContact",
      -  "Basics",
      -  "CheckAccount",
      -  "CheckAccountTransaction",
      -  "CommunicationWay",
      -  "Contact",
      -  "ContactAddress",
      -  "ContactField",
      -  "CreditNote",
      -  "CreditNotePos",
      -  "Export",
      -  "Invoice",
      -  "InvoicePos",
      -  "Layout",
      -  "Order",
      -  "OrderPos",
      -  "Part",
      -  "Report",
      -  "Tag",
      -  "Voucher",
      -  "VoucherPos"
      -]New value: +[
      +  "AccountingContact",
      +  "Basics",
      +  "CheckAccount",
      +  "CheckAccountTransaction",
      +  "CommunicationWay",
      +  "Contact",
      +  "ContactAddress",
      +  "ContactField",
      +  "CreditNote",
      +  "CreditNotePos",
      +  "Export",
      +  "Invoice",
      +  "InvoicePos",
      +  "Layout",
      +  "Order",
      +  "OrderPos",
      +  "Part",
      +  "PrivateTransactionRule",
      +  "Report",
      +  "Tag",
      +  "Voucher",
      +  "VoucherPos"
      +]
  2. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context (catalogue size of 154 operations, API 2.0.0) but says nothing about result ordering, pagination beyond the limit param, or what a match looks like.

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?

The purpose and the 'not covered by a dedicated tool' rule are front-loaded in the first sentence. The trailing enumeration of 22 tags is largely redundant with the schema enum and inflates the length without adding decision value.

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?

With no output schema, the description should clarify what a result contains; it only implies operationIds are returned. For a discovery tool feeding a generic call tool, the missing link between search results and invocation leaves a gap.

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 all four parameters are already documented with examples and enums. The description's tag list merely restates the enum values and adds no new meaning about how tag, kind, query and limit interact.

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 ('Search the sevDesk API catalogue ... for the operationId') and scopes it to 'anything not covered by a dedicated tool', which cleanly separates it from the dedicated list/create/get siblings.

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

Usage Guidelines4/5

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

Gives a clear selection rule: use this when no dedicated tool covers the need. It does not explicitly name the follow-up step (e.g. sevdesk_call / sevdesk_describe_operation) or state when not to use it, so it stops short of full routing guidance.

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