Skip to main content
Glama
davidkotler

icount-mcp

by davidkotler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Cancel document

icount_cancel_document
Destructive

Cancel an existing iCount document to void it permanently. Use when a document must be reversed; confirm the document number first because this action is irreversible.

Instructions

Cancel an existing document (iCount has no hard delete — this is the only way to void one). Irreversible: confirm the document number with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docnumYesThe document number as shown in iCount
reasonNoCancellation reason, stored on the record
doctypeYes
refundCcNoAlso reverse the credit-card charge, if any (fails if there wasn't one)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / docnum / anyOf
      Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  }
+]
    • addedInput schema / properties / docnum / description
      Added value: +"The document number as shown in iCount"
    • removedInput schema / properties / docnum / type
      Removed value: -[
-  "string",
-  "number"
-]
  2. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true, but the description adds the irreversibility warning and instructs to confirm the document number with the user. This is valuable behavioral context beyond the annotations, specifying a safety precaution.

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 sentences with no fluff. It front-loads the core purpose, then adds the critical irreversibility warning. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It provides essential context: the only way to void, irreversibility, and a user-confirmation requirement. It doesn't describe success/failure behavior but that's acceptable for a cancellation tool, and the output schema is absent. The description is sufficient for correct invocation.

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 description coverage is 75% (doctype has no description but has enum). The description adds no parameter-specific information—it doesn't elaborate on docnum, reason, or refundCc. Since the schema already covers most parameters, a baseline of 3 is appropriate.

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 action: "Cancel an existing document". It further differentiates from siblings by noting iCount has no hard delete and this is the only way to void one, which distinguishes it from close, convert, or other document operations.

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?

It explicitly states this is the only way to void a document, giving strong usage context. It doesn't name alternative tools but the statement implies when to use (when voiding) and when not (for other operations). This is clear enough for an agent to select it appropriately.

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

Deploy Server

Other Tools