Skip to main content
Glama
davidkotler

icount-mcp

by davidkotler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Convert document

icount_convert_document

Convert a document to another type. Omit conversionType to list valid options, then provide one to perform the actual conversion.

Instructions

Convert a document to another type (e.g. offer -> order). Omit conversionType to first list the valid conversion options for this document; pass one of those values back in conversionType to perform the actual conversion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docnumYesThe document number as shown in iCount
doctypeYes
conversionTypeNoA value returned by a prior call to this tool without conversionType

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.4/5.0
Behavior3/5

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

Annotations already indicate this is a mutating, non-idempotent operation. The description adds the discovery mechanism (listing options first), which is a behavioral trait beyond annotations. However, it does not disclose side effects such as whether the original document is modified or if a new one is created, nor does it mention error conditions. With annotations present, the added value is moderate, so a 3 is appropriate.

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 zero filler. It front-loads the primary action, then immediately explains the necessary two-step usage. Every sentence earns its place, making it highly concise and well-structured.

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?

The description covers the essential usage pattern completely, including the discovery step and the actual conversion. It does not detail return values (no output schema) or prerequisites like document existence, but these are not critical for an agent to invoke the tool correctly. The two-step workflow is fully explained, which is the main complexity.

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

Parameters4/5

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

Schema coverage is 67% (docnum and conversionType have descriptions; doctype is only an enum). The description adds critical semantics for conversionType by explaining the two-step workflow, which goes beyond the schema's simple 'value returned by a prior call'. This enriches the parameter understanding and justifies a score above the baseline 3.

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 (convert a document to another type) with a concrete example (offer -> order). It distinguishes this tool from siblings like create, cancel, or close because conversion is a unique operation. 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 explains the two-step usage pattern: omit conversionType to list valid options, then pass one back to perform the conversion. This is clear guidance on how to invoke the tool correctly. While it doesn't mention alternatives, the operation is distinct from sibling tools, so no exclusion is needed.

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