Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

List issued invoices

list_issued_invoices
Read-only

List issued invoices newest first and filter by payment status, overdue state, customer, issue date range, or document number; returns compact summaries per document.

Instructions

List issued invoice (vydaná faktura) documents, newest first. Filter by payment status, overdue, customer, issue date range or document number. Returns a compact summary per document; use get_issued_invoice for full detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_issued_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNoPayment status. 'overdue' = unpaid and past due date.
issuedToNoIssue date to (inclusive).
pageSizeNo
partnerIdNoContact ID of the customer (see list_contacts).
issuedFromNoIssue date from (inclusive).
documentNumberNoPart of the document number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), yet the description still adds genuinely new behavior: default sort order ('newest first') and the fact that results are a compact summary rather than full documents. It does not mention pagination defaults or total-count behavior, which is the only meaningful remaining gap.

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 with the core operation and ordering front-loaded, followed by capabilities and then the sibling pointer. No filler, though the parenthetical Czech alias costs a few tokens for marginal benefit.

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 7-parameter, all-optional read list with no output schema, the description supplies what matters: ordering, result granularity ('compact summary'), and the route to full detail. Only pagination semantics are left implicit, and the schema's defaults and bounds partially cover those.

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 coverage is 71% and the description's filter list (payment status, overdue, customer, issue date range, document number) maps almost one-to-one onto parameters the schema already documents, so it adds little new meaning. The two pagination parameters (page, pageSize) remain undocumented in both places, a gap the description does not close.

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?

States a specific verb and resource ('List issued invoice documents'), adds the Czech term for disambiguation, and specifies ordering ('newest first'). It also distinguishes itself from the sibling detail tool get_issued_invoice, so an agent can pick between list and get without opening a schema.

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 names an explicit alternative and the condition that selects it ('use get_issued_invoice for full detail'), which is exactly the list-vs-fetch decision an agent faces. The enumerated filter dimensions also implicitly advertise when this tool is the right query surface.

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