Unofficial Lexware Office MCP Server

Overview Schema Source Related Servers Discussions Admin

get_profile

Read-only

Confirms which Lexware Office account the server is connected to by returning organization, company, tax setup, and small-business status; use it before data changes and to verify API access.

Instructions

Show which Lexware Office account this server is connected to.

One API call. Returns the organization, company name, tax setup and small-business status.

Call it before anything that changes data, so the organization is confirmed rather than assumed. It doubles as the connection check: if it succeeds, the API key works.

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": "get_profile"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.3Nov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile with readOnlyHint=true, and the description adds real context beyond them: it costs one API call and its success is a signal that the API key is valid. It does not describe failure behavior when the key is invalid, which would complete the picture.

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?

Three short sentences, front-loaded with the purpose, then the return payload, then the usage rule. Each sentence carries distinct information with no repetition of the schema or annotations.

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 zero-parameter read tool with no output schema, the description supplies the returned fields and the reason to call it. Nothing an agent needs in order to invoke it correctly is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the description correctly says nothing about inputs. Baseline 4 applies for a parameterless tool.

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?

States a specific verb and resource: shows which Lexware Office account the server is connected to. The second sentence enumerates the returned fields (organization, company name, tax setup, small-business status), which pins the scope tightly and distinguishes it from get_master_data or server_status.

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?

Gives explicit when-to-use guidance: call it before anything that changes data, and use it as the connection/API-key check. It stops short of naming a sibling alternative (e.g. server_status or get_master_data), so the agent must infer the boundary, but the operational timing advice is clear.

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