DokladBot

Vypis dokladu

list_documents

Read-only

Vypis prijatych i vydanych dokladu (uctenky, faktury) s filtrovanim a fulltextem. Vraci strankovany seznam v zestihlenem tvaru (bez souboru dokladu, jen hasImage). Castky po sazbach DPH jsou v mene dokladu.

Input Schema

Name	Required	Description
`page`	No
`type`	No	Skupina typu z menu dashboardu, napr. prijate-faktury, uctenky
`limit`	No	Vychozi 20, max 50
`dateTo`	No	Datum dokladu do (vcetne), YYYY-MM-DD
`search`	No	Fulltext: dodavatel, ICO, cislo dokladu, variabilni symbol
`source`	No	Odkud doklad prisel
`status`	No	Stav schvaleni, vychozi PENDING
`dateFrom`	No	Datum dokladu od (vcetne), YYYY-MM-DD
`exported`	No	true = jen doklady uz nekdy exportovane do souboru (Pohoda XML, Excel, ...), false = jen dosud neexportovane
`companyId`	No	Jen doklady teto firmy (z list_companies)
`unassigned`	No	true = jen doklady bez prirazene firmy
`documentType`	No	Presny typ dokladu

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / documentType / enum

Previous value: -[
-  "faktura",
-  "uctenka",
-  "pokladni_blok",
-  "dobropis",
-  "zalohova_faktura",
-  "vydana_faktura",
-  "objednavka",
-  "smlouva",
-  "jine",
-  "jsd",
-  "vyuctovani"
-]New value: +[
+  "faktura",
+  "uctenka",
+  "pokladni_blok",
+  "dobropis",
+  "zalohova_faktura",
+  "vydana_faktura",
+  "proforma",
+  "objednavka",
+  "smlouva",
+  "jine",
+  "jsd",
+  "vyuctovani"
+]

Changed10 schema fields changedOct 22, 2026

addedInput schema / properties / companyId

Added value: +{
+  "description": "Jen doklady teto firmy (z list_companies)",
+  "type": "string"
+}

addedInput schema / properties / dateFrom

Added value: +{
+  "description": "Datum dokladu od (vcetne), YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / dateTo

Added value: +{
+  "description": "Datum dokladu do (vcetne), YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / documentType

Added value: +{
+  "description": "Presny typ dokladu",
+  "enum": [
+    "faktura",
+    "uctenka",
+    "pokladni_blok",
+    "dobropis",
+    "zalohova_faktura",
+    "vydana_faktura",
+    "objednavka",
+    "smlouva",
+    "jine",
+    "jsd",
+    "vyuctovani"
+  ],
+  "type": "string"
+}

addedInput schema / properties / exported

Added value: +{
+  "description": "true = jen doklady uz nekdy exportovane do souboru (Pohoda XML, Excel, ...), false = jen dosud neexportovane",
+  "type": "boolean"
+}

changedInput schema / properties / search / description

Previous value: -"Fulltext: dodavatel, cislo dokladu, poznamka"New value: +"Fulltext: dodavatel, ICO, cislo dokladu, variabilni symbol"

addedInput schema / properties / source

Added value: +{
+  "description": "Odkud doklad prisel",
+  "enum": [
+    "upload",
+    "email",
+    "whatsapp",
+    "api"
+  ],
+  "type": "string"
+}

changedInput schema / properties / status / enum

Previous value: -[
-  "PENDING",
-  "APPROVED",
-  "REJECTED",
-  "ALL"
-]New value: +[
+  "PENDING",
+  "APPROVED",
+  "SENT",
+  "ERROR",
+  "REJECTED",
+  "ALL"
+]

changedInput schema / properties / type / description

Previous value: -"Typ dokladu, napr. vydana_faktura"New value: +"Skupina typu z menu dashboardu, napr. prijate-faktury, uctenky"

addedInput schema / properties / unassigned

Added value: +{
+  "description": "true = jen doklady bez prirazene firmy",
+  "type": "boolean"
+}

First observedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are paginated, returned in a slimmed form without document files (only hasImage), and VAT-rate amounts are expressed in the document's currency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core purpose, then the return shape, then the currency caveat. No filler; each sentence carries distinct information.

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 12-parameter, no-output-schema list tool, the description covers purpose, return shape (slimmed, hasImage) and a non-obvious data caveat (VAT amounts in document currency). The main gap is the absence of routing guidance among the many sibling list/search tools.

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 92%, so the schema already documents nearly every parameter including enums and formats. The description only alludes to filtering and fulltext generically and adds no syntax or semantics beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Vypis prijatych i vydanych dokladu') and names the concrete document kinds (uctenky, faktury) plus the filtering/fulltext capability. It is clearly a list operation, distinguishable from get_document, but it does not explicitly name the sibling it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 's filtrovanim a fulltextem' – an agent can infer this is the tool for browsing/filtering documents. However, there is no explicit when-to-use vs when-not guidance, and no pointer to get_document for a single record or to search for cross-entity lookup.

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

All DokladBot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?