sevdesk MCP Server

create_tag

Create a tag and assign it to an invoice, voucher, order, or credit note for organization.

Instructions

Create a new tag and attach it to a document (Invoice, Voucher, Order, or CreditNote)

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>",
      "objectId": "<objectId>",
      "objectName": "<objectName>"
    },
    "name": "create_tag"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Name of the tag
`objectId`	Yes	ID of the document to tag
`objectName`	Yes	Type of document to tag

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It mentions attaching to a document, but omits details like side effects, error handling (e.g., duplicate names), or any constraints beyond required parameters.

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 description is a single concise sentence that communicates the core function without waste. Could be slightly improved by front-loading the most critical info, but it is efficient.

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 simple CRUD create tool with fully documented parameters, the description covers the basic purpose. However, it lacks context on return values, error cases (e.g., invalid objectId), and behavior if the tag already exists.

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 the description adds no new meaning beyond the schema. The description reinforces the attach-action, but the schema already defines the parameters adequately.

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 verb (Create), resource (tag), and the specific action (attach to a document), listing the valid document types. This distinguishes it from sibling tools like update_tag and delete_tag.

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 explicit guidance on when to use this tool versus alternatives, such as when not to use it or prerequisites like document existence. The purpose implies creation, but no context for decision-making is provided.

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