Skip to main content
Glama
Sign In

Lexware Office (lexoffice) MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Finalise invoice in Lexware Office (lexoffice)

lexware_office_finalise_invoice
Read-onlyIdempotent

Finalise invoice in the user's own Lexware Office (lexoffice) account from ChatGPT, Claude or any AI agent. Returns how to do it in Lexware Office (lexoffice) step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Lexware Office (lexoffice) Cloud Browser. Lexware Office (lexoffice)'s official API: Yes, Lexware Office has a public REST API with an API key (checked 14 Oct 2026).

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_office_finalise_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already mark it read-only, non-destructive, idempotent, and closed-world. The description adds the crucial behavioral detail that it 'opens nothing by itself' and returns an instructional guide, which is exactly the extra context an agent needs beyond structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is repetitive—'Lexware Office (lexoffice)' appears three times—and includes irrelevant marketing/API-status information ('official API: Yes... checked 14 Oct 2026') that does not help an agent invoke the tool. The useful purpose statement is present but not efficiently structured.

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

Completeness4/5

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

For a zero-parameter guidance tool with no output schema, the description says enough: it returns step-by-step instructions and leaves execution to browser tools. It could be more explicit about preconditions, but it is broadly complete for this tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so there is no parameter semantics burden. The description does not need to explain inputs and the schema has nothing to compensate for.

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 states a specific domain task—finalising an invoice in Lexware Office—and clarifies that the tool itself returns step-by-step instructions rather than performing the action. That clarification rescues what would otherwise be a misleading name, though the opening still reads like an action tool until the second sentence.

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?

It gives a clear implied workflow: call this tool to get screens/buttons/fields, then execute the steps with cotlet_browser_* tools. It does not explicitly compare against alternatives such as cotlet_app_guide or state when not to use it.

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

All Lexware Office (lexoffice) MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources