lexware-mcp-server

Get Recurring Template

lexware_get_recurring_template

Read-onlyIdempotent

Fetch a recurring invoice template by its UUID to access saved billing details for reuse or review.

Instructions

Retrieve a recurring invoice template by ID from Lexware.

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": {
      "id": "<id>"
    },
    "name": "lexware_get_recurring_template"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Recurring template UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.0.0May 26, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds minimal extra beyond 'retrieve', which aligns with annotations. No mention of response format, but annotations compensate.

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, front-loaded sentence with no wasted words. Every word earns its place, conveying the action, resource, and scope efficiently.

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?

For a simple get-by-ID tool with one parameter and comprehensive annotations, the description is complete. It clearly communicates the core operation. No output schema exists, but the agent can infer the return value. No missing context for correct usage.

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% (the 'id' parameter is well-described as 'Recurring template UUID' with format and pattern). The tool description does not add any additional parameter insights beyond what the schema provides, so baseline 3 is appropriate.

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 'Retrieve a recurring invoice template by ID from Lexware' uses a specific verb ('retrieve') and resource ('recurring invoice template'), and clearly distinguishes from sibling tools like `lexware_list_recurring_templates` (list) and `lexware_deeplink_recurring_template` (deeplink).

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

Usage Guidelines4/5

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

The description implies usage: use this tool when you have the UUID to fetch a specific template. It does not explicitly state when not to use it or mention alternatives, but the context from sibling names provides clarity. Lacks explicit exclusion guidance.

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

Deploy Server