Skip to main content
Glama
idoklad-mcp

idoklad-mcp

by honzsik

List proforma invoices

list_proforma_invoices
Read-only

Retrieve proforma invoices newest first, filtered by payment status, overdue, customer, issue date range, or document number, returning compact summaries for each result.

Instructions

List proforma invoice (zálohová faktura) documents, newest first. Filter by payment status, overdue, customer, issue date range or document number. Returns a compact summary per document; use get_proforma_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_proforma_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.4/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 adds genuinely new behavioral facts beyond those: results are sorted newest first and each row is a compact summary rather than a full document. It does not mention pagination behavior or result caps, which leaves a small gap.

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 tightly written sentences: the first establishes the resource and ordering, the second covers filters, return shape, and the escalation path. No redundant restatement of the name or title, and the highest-value information leads.

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 read-only list tool with no output schema, the description supplies what an agent actually needs: ordering, that results are summaries, and where to go for detail. The remaining gap is pagination guidance (page/pageSize defaults and limits are only implicit in the schema).

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?

At 71% schema description coverage, the schema already documents status, date bounds, partnerId and documentNumber. The description's filter list mirrors those parameters without adding format, matching behavior, or default semantics, and page/pageSize remain undocumented in both places.

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 states a specific verb and resource ("List proforma invoice documents"), gives the local-language synonym for disambiguation, and specifies the default ordering ("newest first"). This clearly separates it from the singular get_proforma_invoice sibling.

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?

It enumerates the filterable dimensions (payment status, overdue, customer, issue date range, document number) and explicitly routes to get_proforma_invoice when full detail is needed, since this returns only a compact summary. The condition that selects the alternative is stated outright.

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