Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

List received invoices

list_received_invoices
Read-only

List received invoices newest first, filterable by payment status, overdue, supplier, issue date range, or document number, returning compact summaries for review.

Instructions

List received invoice (přijatá faktura) documents, newest first. Filter by payment status, overdue, supplier, issue date range or document number. Returns a compact summary per document; use get_received_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_received_invoices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNoPayment status. 'overdue' = unpaid and past due date.
issuedToNoIssue date to (inclusive).
pageSizeNo
partnerIdNoContact ID of the supplier (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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description contributes beyond that by disclosing sort order (newest first) and the return shape (compact summary per document, full detail only via the getter). It stops short of stating defaults such as page size or what fields the summary contains, which keeps it below a 5.

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?

Two sentences, zero filler, with the resource scope and ordering front-loaded before the filtering capability and the escalation path to the detail tool. Nothing is repeated from the schema verbatim beyond necessary identifiers.

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?

With no output schema, the description earns its keep by stating that results are compact per-document summaries, and pagination is handled by the schema's page/pageSize. Missing are the summary's field set and whether filters combine with AND semantics, which keeps it just short of fully complete for a 7-parameter listing tool.

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 schema itself documents the key filters (status enum with the overdue clarification, date patterns, supplier contact ID). The description restates the filter dimensions (payment status, overdue, supplier, issue date range, document number) but adds no format or combination guidance, so it is roughly at the baseline-with-partial-coverage level.

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 gives a specific verb and resource ("List received invoice documents") plus a default ordering ("newest first"), and pairs it with the sibling get_received_invoice for detail. An agent can distinguish it from list_issued_invoices and list_proforma_invoices on the resource alone.

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 routes the agent to get_received_invoice when the compact summary is insufficient, which is real when-to-use guidance. It also enumerates the filter dimensions that justify using this listing endpoint, though it does not state when listing is inappropriate (e.g., single-document lookups by ID are only implied).

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