No user-submitted related servers found.
Scored across 31 tools
Most tools map cleanly to a resource+action (invoices_list/get/pdf, credit_notes_list/get/pdf, orders_list/get/pdf, transactions_list/get), and descriptions explicitly steer between near-neighbours (cash_position vs bank_accounts_list, records_summarize vs paging lists). The weak spot is the analytics cluster (records_summarize, profit_and_loss, vat_summary, receivables/payables_aging, cash_position), which all take periods and produce aggregate money figures, and several descriptions point at tools that are not in this set (transaction_book, invoice_finalize, contact_update), which will mislead an agent about what it can actually do.
The dominant convention is sevdesk_<resource>_<action> in snake_case (invoices_list, invoice_get, contacts_search, vouchers_list), applied consistently across all document types. Deviations are few but noticeable: verb-first or verb-verb names (changed_since, reconcile_suggest, records_summarize), and noun-only report tools (cash_position, profit_and_loss, vat_summary, payables_aging) that break the verb pattern.
At 31 tools the surface is heavy, above the comfortable band, though the breadth of sevDesk (contacts, invoices, credit notes, orders, parts, vouchers, bank transactions, plus reporting) largely justifies it. The read list/get/pdf triplets for four document types plus six reporting tools push it toward duplication of surface rather than strictly necessary capability.
The set is essentially read/analyse-only: there is no create, update, finalize, book or save tool for any entity, yet the descriptions repeatedly instruct the agent to use sevdesk_invoice_update_draft, sevdesk_invoice_finalize, sevdesk_transaction_book, sevdesk_transaction_reset, sevdesk_contact_update and sevdesk_document_save, none of which exist here. That leaves documented dead ends (e.g. contacts_next_customer_number exists for creating a contact that cannot be created), so core write-side workflows cannot be completed.