Skip to main content
Glama
lazyants

lexware-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Quotation

lexware_create_quotation

Create a new quotation in Lexware by specifying voucher and expiration dates, customer address, line items with quantities and prices, and total price.

Instructions

Create a new quotation in Lexware.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesQuotation JSON body. Key fields: voucherDate, expirationDate, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 indicate non-readOnly, non-destructive, non-idempotent, and openWorldHint, which the description does not contradict. The description only confirms 'create' (a write operation) but adds no further behavioral context like authentication needs or side effects. With annotations providing the safety profile, the description adds minimal value but is adequate.

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?

The description is a single, clear sentence with no wasted words. It front-loads the core purpose and is appropriately concise for a straightforward creation tool.

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?

Given the complexity of a single nested parameter and minimal annotations, the description is brief but sufficient when combined with the schema. However, it does not elaborate on the returned object or any constraints, and with many sibling tools, more contextual guidance would be beneficial. It meets the minimum viable level.

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?

The input schema has 100% coverage with a description for the 'body' parameter that lists key fields. The tool description does not mention parameters. Per evaluation rules, high schema coverage sets a baseline of 3, even without param info in the description. No additional meaning is provided beyond the schema.

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 explicitly states 'Create a new quotation in Lexware,' using a specific verb and resource. The tool name alone clearly distinguishes it from sibling tools like create_invoice or create_credit_note, which target different document types.

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 offers no guidance on when to use this tool versus alternatives (e.g., create_invoice, create_order_confirmation). It does not mention prerequisites, context, or exclusions, leaving the agent without decision support for choosing this tool.

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