Skip to main content
Glama
davidkotler

icount-mcp

by davidkotler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List clients

icount_list_clients
Read-onlyIdempotent

Fetch all clients from your iCount account, with total and returned counts to clearly show if the list was truncated.

Instructions

List clients in the account. Returns { total, returned, clients } so you can tell when the list was truncated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoDefault 100
detailLevelNo0=basic ... 10=complete (default 1). High values return a lot of data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / detailLevel
      Added value: +{
+  "description": "0=basic ... 10=complete (default 1). High values return a lot of data.",
+  "maximum": 10,
+  "minimum": 0,
+  "type": "integer"
+}
    • changedInput schema / properties / maxResults / description
      Previous value: -"Truncate to this many results (default: all)"New value: +"Default 100"
    • addedInput schema / properties / maxResults / maximum
      Added value: +1000
    • addedInput schema / properties / maxResults / minimum
      Added value: +1
    • changedInput schema / properties / maxResults / type
      Previous value: -"number"New value: +"integer"
  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 cover read-only, idempotent, and non-destructive behavior. The description adds value by revealing the return shape and explicitly warning that results can be truncated, which helps the agent interpret the response.

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?

One focused sentence communicates both the core operation and the return envelope. No filler or redundant restatement of the title.

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 simple list tool with two optional, well-documented parameters and no output schema, the description plus annotations are largely sufficient. It would benefit from hinting about pagination or alternative tools, but that is not a major gap here.

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?

The input schema has 100% description coverage for maxResults and detailLevel, so the description does not need to repeat parameter details. It adds no deeper semantics beyond implying that returned/truncated counts matter, which is already suggested by the schema.

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 states a specific verb and resource: 'List clients in the account.' This clearly distinguishes it from sibling operations like create/update/get/delete client and from broader document tools.

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?

The account-level scope gives clear context for when to use it: when you need to enumerate clients in the account. It does not explicitly name or exclude sibling tools, but the purpose is clear enough to route an agent 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