lexware-mcp-server

List Articles

lexware_list_articles

Read-onlyIdempotent

Retrieve product and service articles from Lexware Office with filters for GTIN, article number, or type, and pagination controls for efficient data access.

Instructions

List all articles with optional pagination.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lexware_list_articles"
  }
}

Input Schema

Name	Required	Description
`gtin`	No	Filter by GTIN/EAN
`page`	No	Page number (0-indexed)
`size`	No	Results per page (max 250)
`type`	No	Filter by article type
`articleNumber`	No	Filter by article number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0May 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate the tool is read-only, idempotent, and non-destructive, covering safety traits. The description adds no behavioral context beyond that (e.g., no mention of rate limits, data freshness, or what 'all articles' entails). It is adequate but does not enhance transparency.

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, efficient sentence that conveys the core purpose and key capability (pagination) with no extraneous words. It is appropriately front-loaded and easy to parse.

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?

The description omits mention of filter parameters (gtin, type, articleNumber) which are available and crucial for targeted queries. Saying 'List all articles' could mislead agents into thinking no filtering is possible. Given the presence of annotations and rich schema, the description does not sufficiently complete the context of the tool's capabilities.

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?

All 5 parameters have schema descriptions covering 100% of their meaning. The description adds no extra semantic value beyond stating 'optional pagination.' The baseline score is 3, and no further information is provided.

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 clearly states the tool's action ('List all articles') and includes the optional pagination feature, which distinguishes it from sibling tools like lexware_get_article that retrieve a single article. The verb-resource combination is specific and unambiguous.

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?

No guidance is given on when to use this tool versus alternatives (e.g., lexware_get_article for a single article, or tools for other resources). There are no explicit when-to-use or when-not-to-use instructions, which could lead to incorrect selection by an agent.

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

Deploy Server