Unofficial Lexware Office MCP Server

Overview Schema Source Related Servers Discussions Admin

get_article

Read-only

Retrieve a Lexware article by ID to read its full details, price data, and version—use it before updating the article or when you already have the ID.

Instructions

Read one article in full, by id.

One API call. Returns the title, description, note, unit, type, the price block and the version.

Use search_articles when you have an article number or a barcode rather than an id. Read this before update_article, which needs the version it reports. An unknown id answers with an error, not an empty record.

The price carries a net and a gross figure with the tax rate between them. leadingPrice says which of the two was entered and which the API computed.

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": {
      "article_id": "<article_id>"
    },
    "name": "get_article"
  }
}

Input Schema

Name	Required	Description	Default
`article_id`	Yes	The article's Lexware id, as returned by search_articles.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.3Nov 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With only readOnlyHint supplied by annotations, the description adds substantial operational context: it is one API call, it returns specific fields including version, and unknown ids produce an error. It also explains the price block's net/gross/leadingPrice semantics, which goes well beyond the annotation.

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 front-loaded with the core purpose and then groups return details, sibling guidance, and price semantics into short paragraphs. Each sentence contributes useful information without repetition or filler.

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

Completeness5/5

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

Although there is no output schema, the description enumerates the returned fields and explains the version and price structure. For a one-parameter read tool with readOnlyHint, this gives the agent everything needed to call it correctly and interpret the response.

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 the schema already defines article_id as the Lexware id returned by search_articles. The description reinforces that article numbers and barcodes are not ids, but this adds only marginal meaning beyond the already thorough schema field description.

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 first sentence, "Read one article in full, by id," states a specific verb, resource, and scope. It clearly distinguishes this single-record read from the sibling search_articles by emphasizing lookup by id and full detail.

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

Usage Guidelines5/5

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

The description explicitly routes article-number or barcode lookups to search_articles and says to read this before update_article because update_article needs the reported version. It also states that an unknown id returns an error rather than an empty record, giving clear exclusions and behavior.

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