sevdesk MCP Server

create_part

Create a new product or service in sevdesk by specifying name, pricing, tax rate, and stock details.

Instructions

Create a new part (product/service) in sevdesk

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`name`	Yes	Name of the part
`stock`	No
`unitId`	No
`taxRate`	No
`priceNet`	No
`partNumber`	No
`priceGross`	No
`stockEnabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

C2.5/5.0

Behavior2/5

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

The description only states the basic creation action, without disclosing behavioral traits like authentication needs, idempotency, or effects of duplicate names. No annotations are present to supplement.

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

Conciseness2/5

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

The description is a single short sentence, but it is under-specified for the complexity of 8 parameters and lacks structure to aid quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters (only 1 described), no output schema, no annotations, and a complex set of sibling tools, the description is far from complete. It only conveys the basic purpose.

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?

Schema description coverage is only 13% (1 of 8 parameters described). The description adds no parameter-level details, failing to compensate for the low coverage.

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 action 'create' and the resource 'part' with additional clarification 'product/service', effectively distinguishing it from sibling tools like create_tag or update_part.

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, such as when to create vs. update a part, or any prerequisites like required fields beyond 'name'.

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