Skip to main content
Glama
Sign In
idoklad-mcp

idoklad-mcp

by honzsik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List credit notes

list_credit_notes
Read-only

List credit note documents newest first and filter by payment status, overdue status, customer, issue date range, or document number. Returns compact summaries, with full detail available separately.

Instructions

List credit note (opravný daňový doklad / dobropis) documents, newest first. Filter by payment status, overdue, customer, issue date range or document number. Returns a compact summary per document; use get_credit_note 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_credit_notes"
  }
}

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.2/5.0
Behavior4/5

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

Annotations already cover the read-only, open-world profile, and the description adds meaningful behavior: results are sorted newest first, each result is a compact summary rather than a full document, and detail requires a follow-up call. It omits pagination limits and whether a total count is returned, which are the remaining behavioral gaps.

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, no filler: identity and ordering first, filters second, return shape and routing last. Every clause carries information an agent needs.

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 list tool with no output schema, the description gives enough to call it correctly and to know what comes back (compact summaries). The one real gap is pagination behavior, which neither the schema descriptions nor the description address.

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?

The description names the filtering axes (payment status, overdue, customer, issue date range, document number), which maps onto the documented schema properties, but adds no format or syntax detail beyond what the schema already gives. Pagination parameters (page, pageSize) are the two properties without schema descriptions, and the description says nothing about them, so it does not fully compensate for the 71% 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?

States a specific verb and resource ('List credit note documents'), includes the local synonyms (opravný daňový doklad / dobropis) that help an agent match user vocabulary, and specifies ordering ('newest first'). It also implicitly separates itself from get_credit_note by promising only a compact summary.

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?

Names the concrete alternative and the condition that selects it ('use get_credit_note for full detail'), and enumerates the filter dimensions that justify using this tool. It stops short of stating when this tool should NOT be used relative to the other list_* siblings, but the guidance is actionable.

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

Deploy Server

Other Tools