sevdesk MCP Server

list_contacts

Retrieve contacts from sevdesk with filters for name, customer number, and pagination settings.

Instructions

List all contacts from sevdesk. Supports filtering by various parameters.

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_contacts"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`depth`	No
`limit`	No
`offset`	No
`customerNumber`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It does not mention pagination (limit/offset), read-only nature, rate limits, or the meaning of 'depth'. Insufficient for a list operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two sentences with no fluff, but underspecified. Could be more informative without adding length. Acceptable but not model of conciseness.

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?

No output schema, so description should detail return format or behavior. It only states 'list all contacts' and mentions filtering, missing pagination, order, or field documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero schema description coverage for 5 parameters. Description only says 'Supports filtering by various parameters' without explaining name, depth, limit, offset, or customerNumber. Adds virtually no value.

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 'List all contacts from sevdesk' with a specific verb and resource. It distinguishes from sibling tool 'get_contact' which retrieves a single contact.

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 alternatives like get_contact or search tools. No mention of prerequisites or context for filtering.

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