Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Pursue to an Order Confirmation

lexware_pursue_order_confirmation

Creates a new order confirmation from an existing quotation using its ID, with Lexware-compatible text formatting for introduction, line items, and remarks.

Instructions

Create a new order confirmation from a quotation via POST /order-confirmations?precedingSalesVoucherId={id}. 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, lineItems, totalPrice, and taxConditions. In introduction, lineItems[].description, and remark, use only Lexware formatting: **bold**, __italic__, and dash-prefixed list items separated by newlines.
precedingSalesVoucherIdYesUUID of the preceding quotation that this order confirmation is pursued from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.3.0
    • changedInput schema / properties / body / description
      Previous value: -"Order confirmation JSON body. Same shape as lexware_create_order_confirmation. See Lexware API docs for full schema."New value: +"Order confirmation JSON body with voucherDate, address, lineItems, totalPrice, and taxConditions. In introduction, lineItems[].description, and remark, use only Lexware formatting: **bold**, __italic__, and dash-prefixed list items separated by newlines."
  2. First observedv3.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety/mutation profile is covered. The description contributes genuine extra context — the Lexware formatting rules for introduction, lineItems[].description, and remark — but says nothing about auth, rate limits, or response behavior.

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 action and endpoint, with zero filler. The formatting rule is packed into the second sentence without redundancy.

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 mutation tool with a nested body and no output schema, the definition covers the action and formatting constraints but leaves the response shape and permission requirements unstated. It is adequate but not complete against the tool's complexity.

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 schema already documents both parameters and the body's fields. The description's formatting note largely restates the schema's own body description rather than adding new meaning, so the baseline 3 applies.

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?

The description names a specific verb+resource+origin ('create a new order confirmation from a quotation'), which is more informative than a plain create. It implicitly distinguishes the pursue flow from create_order_confirmation, but never names the sibling explicitly to make the distinction airtight.

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 'from a quotation' constraint implies this tool is for converting an existing quotation, and the API path makes the flow concrete. However, there is no explicit when-to-use guidance or statement of when to prefer create_order_confirmation over this one, leaving routing to inference.

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