Kema Invoice

Create company

create_company

Create a customer company for the tenant. A VAT/tax id is required later to bill it as B2B.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City.
`name`	Yes	Company display name.
`email`	No	Billing email address.
`phone`	No	Phone number, any format.
`siren`	No	French SIREN, 9 digits.
`tax_id`	No	VAT number, e.g. FR12345678901.
`country`	No	ISO 3166-1 alpha-2 country code, e.g. FR.
`website`	No	Website URL, including the scheme (https://).
`postal_code`	No	Postal code.
`street_address`	No	Street address (number and street).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Company UUID.
`name`	Yes	Display name.
`email`	Yes	Billing email.
`siren`	Yes	French SIREN (9 digits).
`tax_id`	Yes	VAT number.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 7, 2026

addedInput schema / properties / city / description
```
Added value: +"City."
```

changedInput schema / properties / country / description

Previous value: -"ISO country, e.g. FR."New value: +"ISO 3166-1 alpha-2 country code, e.g. FR."

addedInput schema / properties / email / description
```
Added value: +"Billing email address."
```
addedInput schema / properties / name / description
```
Added value: +"Company display name."
```
addedInput schema / properties / phone / description
```
Added value: +"Phone number, any format."
```
addedInput schema / properties / postal_code / description
```
Added value: +"Postal code."
```
addedInput schema / properties / street_address / description
```
Added value: +"Street address (number and street)."
```

changedInput schema / properties / tax_id / description

Previous value: -"VAT number."New value: +"VAT number, e.g. FR12345678901."

addedInput schema / properties / website / description

Added value: +"Website URL, including the scheme (https://)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "email": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Billing email."
+    },
+    "id": {
+      "description": "Company UUID.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "siren": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "French SIREN (9 digits)."
+    },
+    "tax_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "VAT number."
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "email",
+    "tax_id",
+    "siren"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Description adds meaningful behavioral context by clarifying that a VAT/tax id is not needed at creation time but will be required later for B2B billing. This supplements the annotations and does not contradict them.

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?

Two concise sentences with the primary purpose front-loaded. There is no redundant information or unnecessary detail.

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?

Given the simple flat parameter structure and presence of an output schema, the description provides sufficient context for correct usage, including the notable tax_id timing caveat.

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 schema already describes all 10 parameters with 100% coverage. The description adds extra meaning to the tax_id parameter by explaining that it is required later for B2B billing, which is not evident from the schema alone.

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?

Clearly states the action ('create') and the resource ('customer company for the tenant'), distinguishing it from sibling tools like update_company, get_company, list_companies, and delete_company.

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 verb 'create' implies when to use the tool, and the note about tax_id being required later for B2B billing provides useful context. However, it does not explicitly mention alternatives or 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 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.