Kema Invoice

Get settings (read-only)

get_settings

Read-only

Read-only snapshot of the tenant's invoicing settings: legal identity, fiscal country and regime, default VAT rate and payment terms, billing email, and the caller's UI language. Settings can only be CHANGED from the app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`tax_id`	Yes	Tenant VAT number.
`legal_form`	Yes	Legal form (e.g. SAS, SARL, EI).
`legal_name`	Yes	Registered legal name of the tenant.
`tax_regime`	Yes	VAT regime: normal or franchise_en_base.
`tax_country`	Yes	Fiscal country, ISO 3166-1 alpha-2.
`display_name`	Yes	Tenant display name.
`billing_email`	Yes	Email printed on documents.
`preferred_language`	Yes	Caller's UI language (ISO 639-1).
`default_vat_rate_key`	Yes	Default VAT rate key applied to new lines.
`default_payment_terms`	Yes	Default payment terms for new documents.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "billing_email": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Email printed on documents."
+    },
+    "default_payment_terms": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Default payment terms for new documents."
+    },
+    "default_vat_rate_key": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Default VAT rate key applied to new lines."
+    },
+    "display_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Tenant display name."
+    },
+    "legal_form": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Legal form (e.g. SAS, SARL, EI)."
+    },
+    "legal_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Registered legal name of the tenant."
+    },
+    "preferred_language": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Caller's UI language (ISO 639-1)."
+    },
+    "tax_country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Fiscal country, ISO 3166-1 alpha-2."
+    },
+    "tax_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Tenant VAT number."
+    },
+    "tax_regime": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "VAT regime: normal or franchise_en_base."
+    }
+  },
+  "required": [
+    "legal_name",
+    "display_name",
+    "legal_form",
+    "tax_country",
+    "tax_id",
+    "tax_regime",
+    "default_vat_rate_key",
+    "default_payment_terms",
+    "billing_email",
+    "preferred_language"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The readOnlyHint annotation already signals no side effects, and the description reinforces this by repeating 'read-only' and adding that changes must happen in the app. No rate limits or auth details are given, but the annotation lowers the bar for additional behavioral disclosure.

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 two concise sentences with no redundancy. It front-loads the read-only nature and then lists the included setting categories, providing maximum information in minimal space.

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?

The description is complete enough for a zero-parameter read-only tool: it names the resource (tenant invoicing settings) and the main content areas. It does not detail the output schema, but the absence of parameters and the clear snapshot framing make the behavior predictable.

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 no parameter-level documentation is needed. The baseline for zero-parameter tools is 4, and the description gives sufficient context about what the returned settings snapshot will contain.

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 purpose as retrieving a read-only snapshot of tenant invoicing settings and enumerates the specific categories included. The title further reinforces this by naming the operation and its read-only nature.

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 when to use it—when a read-only view of settings is needed—and explicitly notes that settings can only be changed from the app, which directs users away from attempting modifications via the API. It does not explicitly contrast with sibling tools, but the unique scope makes misuse unlikely.

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

All Kema Invoice tools Inspect

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.