Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Order Confirmation

lexware_create_order_confirmation

Create a new order confirmation in Lexware as a draft or finalize it at creation by setting finalize=true.

Instructions

Create a new order confirmation 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
bodyYesOrder confirmation 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 order confirmation 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: -"Order confirmation 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: +"Order confirmation 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 order confirmation at creation via ?finalize=true. When false or omitted, create as draft.",
+  "type": "boolean"
+}
  2. First observedv3.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare this is a non-destructive, non-idempotent write operation. The description adds value by clarifying draft-versus-finalize behavior and the Lexware-specific formatting required for introduction, lineItems[].description, and remark. It stops short of explaining what finalizing does downstream (locking, sending), but it is consistent with annotations and adds useful context.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and finalize semantics, followed by a compact formatting constraint. No filler sentences.

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 tool with a nested freeform body and no output schema, the description covers the critical behavioral flag (finalize) and the non-obvious formatting requirement. The schema's body description supplies the field-level detail, so the combined definition is nearly complete, though it could clarify finalize side effects.

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%, and both finalize and body already carry detailed schema descriptions, including the same formatting rule. The tool description repeats rather than extends that information, so it adds no parameter meaning beyond the schema.

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 ('Create') and resource ('order confirmation'), so an agent can distinguish it from siblings like create_invoice or create_quotation. However, it does not explicitly name or contrast any sibling, leaving sibling differentiation implicit.

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?

The description explains the finalize parameter but gives no guidance on when to create an order confirmation versus other voucher types (invoice, quotation, delivery note). There are no stated prerequisites, exclusions, or alternatives.

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