tezga-mcp

Lista dokumenata

tezga_lista_dokumenata

Lists fiscal documents for an account and applies optional query filters such as date range or status.

Instructions

Lista fiskalnih dokumenata naloga, sa opcionim filterima (prosleđuju se kao query parametri).

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": "tezga_lista_dokumenata"
  }
}

Input Schema

Name	Required	Description	Default
`filteri`	No	Opcioni filteri, npr. { od, do, status }

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only list operation through 'Lista', but does not disclose pagination, result limits, authentication requirements, or return behavior.

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?

The description is a single front-loaded sentence with no wasted wording. It communicates the core action, resource, and filter behavior efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complexity is low with one optional nested parameter, and the schema is fully documented. However, with no annotations and no output schema, the description does not explain return contents, pagination, or result limits, leaving clear gaps for an agent.

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 100%, and the schema already documents the optional 'filteri' object with examples such as { od, do, status }. The description only restates that filters are optional and passed as query parameters, so baseline 3 is appropriate.

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 action and resource: listing fiscal documents for an account/order, with optional filters. It is clear enough to distinguish listing from issuing or refunding, but it does not explicitly differentiate itself from sibling tezga_stanje_dokumenta.

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

Usage Guidelines2/5

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

The only usage guidance is that filters are optional and passed as query parameters. It does not say when to use this tool instead of tezga_stanje_dokumenta or when filtering is appropriate.

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

Deploy Server