Kema Invoice

Reject quote

reject_quote

Destructive

Mark a Sent quote as Rejected by the client. This ends the quote's lifecycle. Call with confirm:true to apply; without it, returns a preview.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`confirm`	No	Must be true to reject. Omit/false to preview only.
`quote_id`	Yes	The Sent quote UUID.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Quote UUID.
`note`	No	Next-step guidance, present on preview responses.
`type`	No	Document type: invoice, credit_note, provision or quote.
`status`	No	Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.
`preview`	No	True when the call was a preview (confirm omitted or false): nothing was changed.
`currency`	No	ISO 4217 currency code (EUR, USD, GBP or CHF).
`due_date`	No	Due date, YYYY-MM-DD.
`net_total`	No	Total excl. VAT, in the document currency.
`tax_total`	No	VAT amount, in the document currency.
`issue_date`	No	Issue date, YYYY-MM-DD.
`gross_total`	No	Total incl. VAT, in the document currency.
`valid_until`	No	Validity limit, YYYY-MM-DD.
`would_reject`	No	Quote that would be rejected (preview only).
`invoice_number`	No	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"
+    },
+    "note": {
+      "description": "Next-step guidance, present on preview responses.",
+      "type": "string"
+    },
+    "preview": {
+      "description": "True when the call was a preview (confirm omitted or false): nothing was changed.",
+      "type": "boolean"
+    },
+    "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."
+    },
+    "would_reject": {
+      "additionalProperties": false,
+      "description": "Quote that would be rejected (preview only).",
+      "properties": {
+        "gross_total": {
+          "description": "Total incl. VAT, in the document currency.",
+          "type": "number"
+        },
+        "id": {
+          "description": "Document UUID.",
+          "type": "string"
+        },
+        "invoice_number": {
+          "description": "Human-readable document number.",
+          "type": "string"
+        },
+        "status": {
+          "description": "Document status: Draft, Sent, Paid, Overdue, Cancelled, Rectified, Accepted, Rejected or Expired.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "invoice_number",
+        "status",
+        "gross_total"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Description transparently reveals the destructive nature ('ends the quote's lifecycle') and the preview mechanism when confirm is false. This aligns with the destructiveHint annotation and adds meaningful behavioral context beyond the schema.

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 no redundant or vague wording. Every sentence carries essential information about the action, effect, and confirm behavior.

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?

For a simple parameter set (quote_id, confirm) plus output schema, the description sufficiently explains the purpose, effect, and preview mode. No additional context is needed to call the tool correctly.

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

Parameters3/5

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

Schema already provides full descriptions for both parameters (quote_id: 'The Sent quote UUID'; confirm: 'Must be true to reject. Omit/false to preview only.'). The description repeats the confirm semantics without adding new detail, so no additional value beyond 100% schema coverage.

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?

Description clearly states the action ('Mark a Sent quote as Rejected') and the resource ('Sent quote'), with the consequential effect 'ends the quote's lifecycle'. It distinguishes from sibling actions like accept_quote by targeting rejection.

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?

Gives concrete usage instructions for the confirm parameter ('Call with confirm:true to apply; without it, returns a preview'). It defines when to apply versus preview, though it does not explicitly compare to alternative quote-related tools.

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.