Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Delivery Note

lexware_create_delivery_note

Create a new Lexware delivery note as a draft or finalize it immediately. Provide delivery date, address, line items, total price, and tax conditions to document shipped goods.

Instructions

Create a new delivery note in Lexware; finalize=true finalizes at creation, false or omitted creates a draft. In introduction, lineItems[].description, and remark, use only Lexware formatting: bold, italic, and dash-prefixed list items separated by newlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesDelivery note JSON body with voucherDate, address (contactId or manual fields), lineItems (name, quantity, unitPrice), totalPrice, and taxConditions. In introduction, lineItems[].description, and remark, use only Lexware formatting: **bold**, __italic__, and dash-prefixed list items separated by newlines.
finalizeNoWhen true, finalize the delivery note at creation via ?finalize=true. When false or omitted, create as draft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.3.0
    • changedInput schema / properties / body / description
      Previous value: -"Delivery note JSON body. Key fields: voucherDate, address (object with contactId or manual fields), lineItems (array with name, quantity, unitPrice, etc.), totalPrice (object), taxConditions (object). See Lexware API docs for full schema."New value: +"Delivery note JSON body with voucherDate, address (contactId or manual fields), lineItems (name, quantity, unitPrice), totalPrice, and taxConditions. In introduction, lineItems[].description, and remark, use only Lexware formatting: **bold**, __italic__, and dash-prefixed list items separated by newlines."
    • addedInput schema / properties / finalize
      Added value: +{
+  "description": "When true, finalize the delivery note at creation via ?finalize=true. When false or omitted, create as draft.",
+  "type": "boolean"
+}
  2. First observedv3.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds real value beyond that: it explains the draft-vs-finalized state transition controlled by `finalize`, which annotations do not convey, plus a mandatory formatting constraint for text fields.

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?

Two sentences, front-loaded with the core purpose, and the finalize rule is stated compactly. The formatting sentence is longer but encodes a hard requirement that is easy to get wrong, so it earns its space despite some duplication with the schema.

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

Completeness4/5

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

For a two-parameter tool with a nested body object at full schema coverage, the description covers the mutation intent, the finalize state behavior, and the text-formatting constraint. With no output schema it does not describe the return payload, but nothing critical for correct invocation is missing.

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 coverage is 100%, and both parameters carry rich descriptions that already document `finalize` semantics and the Lexware formatting rules. The description largely restates what the schema provides for `finalize` and repeats the formatting instruction verbatim, adding little beyond the structured fields, so the baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create a new delivery note in Lexware") so the agent knows exactly what operation this performs. It does not, however, differentiate itself from the many sibling create tools (create_invoice, create_quotation, create_order_confirmation, create_credit_note), though the resource noun does most of that work implicitly.

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

Usage Guidelines3/5

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

The description gives a clear usage decision for the `finalize` flag (true = finalize at creation, false/omitted = draft), which is genuine when-to-use guidance. It stops short of naming any alternative tool or stating when to prefer creating a delivery note over a related voucher type.

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

Deploy Server

Other Tools