Skip to main content
Glama
davidkotler

icount-mcp

by davidkotler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get client open documents

icount_get_client_open_docs
Read-onlyIdempotent

Retrieve a client's open, unpaid documents and outstanding balance by client ID, email, or name.

Instructions

List one client's open (unpaid/unsettled) documents — their outstanding balance. Requires a client: pass clientId (preferred), email, or clientName. There is no all-clients mode; for that, use icount_search_documents with status 0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoIdentify the client by email instead of id
doctypeNo
clientIdNoPreferred identifier, from icount_list_clients
getItemsNoInclude line items on each document
clientNameNoIdentify the client by exact name instead of id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / clientId / description
      Added value: +"Preferred identifier, from icount_list_clients"
    • changedInput schema / properties / clientName / description
      Previous value: -"Filter by client name instead of id"New value: +"Identify the client by exact name instead of id"
    • changedInput schema / properties / email / description
      Previous value: -"Filter by client email instead of id"New value: +"Identify the client by email instead of id"
  2. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, and non-destructive nature of this tool. The description adds value beyond annotations by stating that a client identifier is mandatory, defining 'open' as unpaid/unsettled, and disclosing the absence of an all-clients mode. It also clarifies that the result represents an outstanding balance, which is useful operational context.

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 three sentences long and front-loaded with the core purpose, followed by identifier options and the sibling alternative. There is no filler, and every sentence contributes to correct tool selection and invocation.

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?

For a 5-parameter tool with no output schema, the description covers the key operational constraints: mandatory client reference, no all-clients mode, and the meaning of 'open'. It does not detail the response shape beyond outstanding balance, but the core use case and invocation requirements are sufficiently specified.

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?

With 80% schema description coverage, most parameters are already documented in the input schema. The description adds extra meaning by marking clientId as the preferred identifier and presenting email/clientName as alternatives, which is not obvious from the schema's 0 required parameters. It does not cover doctype, but the enum provides sufficient constraints.

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 states a specific verb and resource ('List one client's open documents') and further clarifies 'open' as unpaid/unsettled. It explicitly differentiates from the sibling icount_search_documents by noting there is no all-clients mode and directing the agent to that alternative. This makes the tool's purpose distinct from icount_get_document and icount_list_clients.

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 gives explicit when-to-use guidance: the caller must provide one of clientId, email, or clientName, with clientId preferred. It also provides a when-not condition by stating 'There is no all-clients mode; for that, use icount_search_documents with status 0.' This clearly orients the agent among sibling tools.

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