Skip to main content
Glama

Kema Invoice

by com.kema-studio
OverviewDiscussionsAdmin

Delete client billing profile

delete_invoice_client_profile
Destructive

Remove a company's invoicing defaults (the company itself is untouched). Call with confirm:true to actually delete; without it, returns a preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to delete. Omit/false to preview only.
company_idYesCompany UUID whose billing profile is deleted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoNext-step guidance, present on preview responses.
deletedNoTrue once the profile is deleted (after confirm:true).
previewNoTrue when the call was a preview (confirm omitted or false): nothing was changed.
company_idNoCompany UUID the profile belonged to (after confirm:true).
would_deleteNoProfile that would be deleted (preview only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / company_id / description
      Added value: +"Company UUID whose billing profile is deleted."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "company_id": {
+      "description": "Company UUID the profile belonged to (after confirm:true).",
+      "type": "string"
+    },
+    "deleted": {
+      "description": "True once the profile is deleted (after confirm:true).",
+      "type": "boolean"
+    },
+    "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"
+    },
+    "would_delete": {
+      "additionalProperties": false,
+      "description": "Profile that would be deleted (preview only).",
+      "properties": {
+        "company": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Company name, null when not resolvable."
+        },
+        "company_id": {
+          "description": "Company UUID.",
+          "type": "string"
+        },
+        "delivery_channel": {
+          "description": "Delivery channel: Email, e-Invoice or Manual.",
+          "type": "string"
+        },
+        "id": {
+          "description": "Profile UUID.",
+          "type": "string"
+        },
+        "invoice_prefix": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Custom invoice number prefix, null for the tenant default."
+        },
+        "payment_terms": {
+          "description": "Payment terms: Net-15, Net-30, Net-60, Net-90 or Due on Receipt.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "company_id",
+        "company",
+        "payment_terms",
+        "delivery_channel",
+        "invoice_prefix"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

The destructive nature is disclosed through annotations and reinforced by the description, which also clarifies that only the billing profile is affected and the company remains intact. The confirm flag behavior is transparent.

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 superfluous content. The essential information about destructive scope and confirmation requirement is delivered efficiently.

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 destructive tool with a confirmation parameter, the description covers the action, the scope limitation, and the exact usage of the confirm flag. It is self-contained and sufficient for an agent to invoke it correctly.

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?

Both parameters are fully described in the schema, and the description adds crucial behavioral meaning to confirm by explaining the actual-delete vs preview distinction. This goes beyond the schema's basic 'Must be true to delete' explanation.

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 removes a company's invoicing defaults and explicitly notes the company itself is untouched, distinguishing it from delete_company. The verb and resource are specific and 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?

The description explicitly instructs to call with confirm:true to actually delete and without it to preview, providing direct usage guidance for the key parameter. This leaves no ambiguity about how to invoke the destructive action safely.

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

All Kema Invoice toolsInspect
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.

Resources