Kema Invoice

Get company

get_company

Read-only

Fetch one customer company with the full billing-relevant record: legal identity, VAT/SIREN, address, contact details, and client profile classification.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company_id`	Yes	Company UUID (use list_companies to resolve).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Company UUID.
`city`	Yes	City.
`name`	Yes	Display name.
`email`	Yes	Billing email.
`phone`	Yes	Phone number.
`siren`	Yes	French SIREN (9 digits).
`state`	Yes	State or region.
`tax_id`	Yes	VAT number.
`country`	Yes	ISO 3166-1 alpha-2 country code.
`website`	Yes	Website URL.
`legal_name`	Yes	Registered legal name, when different from name.
`postal_code`	Yes	Postal code.
`account_type`	Yes	CRM account type.
`account_status`	Yes	CRM account status.
`client_profile`	Yes	Client classification: pm (legal entity), pp_pro (sole trader) or consumer.
`street_address`	Yes	Street address.

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": {
+    "account_status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "CRM account status."
+    },
+    "account_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "CRM account type."
+    },
+    "city": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "City."
+    },
+    "client_profile": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Client classification: pm (legal entity), pp_pro (sole trader) or consumer."
+    },
+    "country": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "ISO 3166-1 alpha-2 country code."
+    },
+    "email": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Billing email."
+    },
+    "id": {
+      "description": "Company UUID.",
+      "type": "string"
+    },
+    "legal_name": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Registered legal name, when different from name."
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "phone": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Phone number."
+    },
+    "postal_code": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Postal code."
+    },
+    "siren": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "French SIREN (9 digits)."
+    },
+    "state": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "State or region."
+    },
+    "street_address": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Street address."
+    },
+    "tax_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "VAT number."
+    },
+    "website": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Website URL."
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "email",
+    "tax_id",
+    "siren",
+    "country",
+    "client_profile",
+    "legal_name",
+    "phone",
+    "street_address",
+    "city",
+    "state",
+    "postal_code",
+    "website",
+    "account_type",
+    "account_status"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description aligns with the readOnlyHint annotation ('Fetch' implies no side effects) and openWorldHint=false. It discloses the scope of returned data, and no contradictions exist.

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 a single concise sentence, front-loaded with the action and resource, and includes necessary details without fluff.

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?

The output schema exists, so return values are defined externally. The description lists key fields included, and for a read-only operation with a closed world hint, no additional context (like error cases or permissions) is necessary.

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

Parameters5/5

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

The single parameter company_id has a helpful description including format (UUID) and a cross-reference to list_companies for resolution. This fully covers the required parameter with additional context.

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 fetches one customer company, with a specific verb and resource. It lists the included data fields (legal identity, VAT/SIREN, etc.), distinguishing it from list_companies (multiple) and update_company (modify).

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 usage for retrieving a single company by ID, and the parameter hint 'use list_companies to resolve' gives guidance. However, it does not explicitly contrast with list_companies or other retrieval tools, leaving some room for ambiguity in a large sibling set.

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.