Kema Invoice

Accept quote

accept_quote

Destructive

Mark a Sent quote as Accepted by the client. Follow up with convert_quote_to_invoice to bill it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`quote_id`	Yes	The Sent quote UUID.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Quote UUID.
`type`	Yes	Document type: invoice, credit_note, provision or quote.
`status`	Yes	Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.
`currency`	Yes	ISO 4217 currency code (EUR, USD, GBP or CHF).
`due_date`	Yes	Due date, YYYY-MM-DD.
`net_total`	Yes	Total excl. VAT, in the document currency.
`tax_total`	Yes	VAT amount, in the document currency.
`issue_date`	Yes	Issue date, YYYY-MM-DD.
`gross_total`	Yes	Total incl. VAT, in the document currency.
`valid_until`	Yes	Validity limit, YYYY-MM-DD.
`invoice_number`	Yes	Quote number (own series).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / quote_id / description

Previous value: -"The quote UUID."New value: +"The Sent quote UUID."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "currency": {
+      "description": "ISO 4217 currency code (EUR, USD, GBP or CHF).",
+      "type": "string"
+    },
+    "due_date": {
+      "description": "Due date, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "gross_total": {
+      "description": "Total incl. VAT, in the document currency.",
+      "type": "number"
+    },
+    "id": {
+      "description": "Quote UUID.",
+      "type": "string"
+    },
+    "invoice_number": {
+      "description": "Quote number (own series).",
+      "type": "string"
+    },
+    "issue_date": {
+      "description": "Issue date, YYYY-MM-DD.",
+      "type": "string"
+    },
+    "net_total": {
+      "description": "Total excl. VAT, in the document currency.",
+      "type": "number"
+    },
+    "status": {
+      "description": "Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.",
+      "type": "string"
+    },
+    "tax_total": {
+      "description": "VAT amount, in the document currency.",
+      "type": "number"
+    },
+    "type": {
+      "description": "Document type: invoice, credit_note, provision or quote.",
+      "type": "string"
+    },
+    "valid_until": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Validity limit, YYYY-MM-DD."
+    }
+  },
+  "required": [
+    "id",
+    "invoice_number",
+    "type",
+    "status",
+    "issue_date",
+    "due_date",
+    "valid_until",
+    "currency",
+    "net_total",
+    "tax_total",
+    "gross_total"
+  ],
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A5/5.0

Behavior5/5

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

The annotation already indicates destructiveHint=true and readOnlyHint=false. The description adds that it changes the quote's state to Accepted, which aligns with the destructive nature. This transparency is sufficient and consistent.

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 redundant information. It directly states the action and the recommended follow-up, making it highly efficient and well-structured.

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 presence of an output schema and the simplicity of the operation, the description provides all necessary context for an agent to understand when and how to use the tool. It also names the related sibling tool for the next step, completing the workflow context.

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 required parameter quote_id is fully described in the schema as 'The Sent quote UUID.' No additional clarification is needed, and the parameter is straightforward and unambiguous.

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 function: marking a Sent quote as Accepted. It also distinguishes it from sibling tools by referencing the follow-up convert_quote_to_invoice, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs when to use this tool (after a quote is sent and client accepts) and provides a direct next step (convert_quote_to_invoice). This gives clear guidance and routes the agent to the correct sibling tool.

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.