Skip to main content
Glama
Sign In
office-books-mcp

office-books-mcp

by mjmirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Company profile

get_profile
Read-only

Reads the connected Lexware Office company profile, returning company name, tax type, small business status and connected user. Use it to confirm which account and tax setup an AI assistant is working with.

Instructions

Read the connected Lexware Office company profile: company name, tax type, small business status and connected user.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value by disclosing the returned payload fields, which matters because no output schema exists. It omits edge behavior (e.g., what happens when no company is connected), keeping it from a 5.

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?

A single front-loaded sentence that leads with the action and resource, then the returned fields. No filler, no restatement of the name, nothing to trim.

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 read with no output schema, listing the returned fields fills the main gap an agent would otherwise have. The only omission is failure-mode behavior when no Lexware Office connection exists, which is a minor residual gap given the annotations already signal an external service.

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 input schema has zero properties, so per the baseline this scores 4. The description correctly implies there is nothing to supply, adding no misleading input expectations.

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 ("Read") and resource ("connected Lexware Office company profile") and enumerates the exact contents returned: company name, tax type, small business status, connected user. This clearly separates it from the collection-oriented siblings like list_contacts or get_voucher.

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?

The word "connected" implies the single-account context and the resource name implies when you'd reach for it (account/tenant metadata rather than a specific record). There is no explicit when-to-use versus when-not guidance or named alternative, but for a zero-parameter profile read the implied usage is unambiguous.

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

Deploy Server

Other Tools