icount-mcp

Search documents

icount_search_documents

Read-onlyIdempotent

Search iCount documents by type, status, client, date range, or document number. Apply at least one filter to retrieve matching documents or an empty result.

Instructions

Search existing iCount documents by type, status, client, date range, or document number. At least one filter is required. A search that matches nothing returns { docs: [], matched: 0 } — that is a normal empty result, not an error. A very broad date range can be rejected as too_many_results; narrow it rather than raising maxResults, which does not lift that limit.

Input Schema

TableJSON Schema

Name	Required	Description
`vatId`	No
`docnum`	No
`offset`	No	Pagination offset
`status`	No	0=open, 1=closed, 2=partially closed
`doctype`	No
`endDate`	No	Range end
`clientId`	No
`sortField`	No
`sortOrder`	No
`startDate`	No	Range start
`clientName`	No
`maxResults`	No	Default 100
`clientEmail`	No
`detailLevel`	No	0=basic ... 10=complete (default 1). High values return a lot of data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.3.2Sep 17, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedInput schema / properties / detailLevel / description
```
Previous value: -"0=basic ... 10=complete (default 1)"New value: +"0=basic ... 10=complete (default 1). High values return a lot of data."
```
- changedInput schema / properties / detailLevel / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / docnum / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / docnum / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / docnum / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / endDate / description
```
Previous value: -"YYYY-MM-DD"New value: +"Range end"
```
- addedInput schema / properties / endDate / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / maxResults / description
```
Added value: +"Default 100"
```
- changedInput schema / properties / maxResults / minimum
```
Previous value: -0New value: +1
```
- changedInput schema / properties / maxResults / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- changedInput schema / properties / offset / type
```
Previous value: -"number"New value: +"integer"
```
- changedInput schema / properties / startDate / description
```
Previous value: -"YYYY-MM-DD"New value: +"Range start"
```
- addedInput schema / properties / startDate / pattern
```
Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
```
- addedInput schema / properties / status / anyOf
```
Added value: +[
+  {
+    "const": 0,
+    "type": "number"
+  },
+  {
+    "const": 1,
+    "type": "number"
+  },
+  {
+    "const": 2,
+    "type": "number"
+  }
+]
```
- removedInput schema / properties / status / enum
```
Removed value: -[
-  0,
-  1,
-  2
-]
```
- removedInput schema / properties / status / type
```
Removed value: -"number"
```
First observedv0.2.0Sep 17, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds valuable behavioral context beyond the annotations: it specifies the exact empty-result format (`{ docs: [], matched: 0 }`) and explains that a broad date range may be rejected as `too_many_results`, with guidance to narrow rather than increase maxResults. This complements the readOnlyHint, openWorldHint, and idempotentHint annotations without contradiction.

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 concise (two sentences) and front-loaded with the core purpose. The second sentence delivers crucial usage warnings without unnecessary fluff. Every sentence earns its place, making it efficient for an agent to parse.

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

Completeness3/5

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

Given the tool has 14 parameters and no output schema, the description covers the essential usage constraints (at least one filter, empty-result format, too_many_results handling) but leaves parameter-level details to the schema, which is only 43% covered. It does not explain response structure beyond the empty case, nor does it clarify defaults for maxResults or detailLevel (though those are in schema descriptions). It is adequate but not comprehensive for such a parameter-rich tool.

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

Parameters2/5

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

With only 43% schema description coverage, the description should compensate for the many undocumented parameters (vatId, docnum, clientId, clientName, clientEmail, sortField, sortOrder). It only lists filter categories generically (type, status, client, date range, document number) without explaining individual parameter semantics or their relationships. This is insufficient given the low coverage.

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's function: searching existing iCount documents by multiple specific filter criteria (type, status, client, date range, document number). It distinguishes itself from siblings like icount_get_document (which retrieves a single document) and icount_get_client_open_docs (which is client-specific), making the purpose unambiguous.

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 that at least one filter is required, which is a key usage constraint. It also advises on handling 'too_many_results' by narrowing the date range rather than raising maxResults. However, it does not explicitly mention when to use this tool versus alternatives (e.g., using icount_get_document for a known document ID), though the purpose is clear enough that an agent can infer it.

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

Deploy Server

Search documents

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools