Skip to main content
Glama
Seyn-Labs

mcp-ai-fiskalizacija

by Seyn-Labs

Izradi i fiskaliziraj račun

solo_create_invoice

Creates and fiscalizes invoices via solo.com.hr, automatically assigning next invoice number and generating fiscal codes (ZKI/JIR) for compliant B2B, B2G, or B2C transactions.

Instructions

Izrađuje novi račun preko solo.com.hr servisa. Solo automatski dodjeljuje sljedeći broj računa i fiskalizira ga (ZKI/JIR) ako je fiskalizacija uključena u Solo postavkama. Vraća broj računa, iznose, ZKI/JIR i link na PDF. Za B2B/B2G kupce obavezni su kupac_naziv, kupac_oib i kpd oznaka po stavci.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tip_uslugeNoID tipa usluge iz Solo postavki (Usluge nakon prijave). Zadano 1.
tip_racunaNoTip računa: 1=R1, 2=R2, 3=bez oznake, 4=avansni. Zadano 1 (R1).
tip_kupcaYesTip kupca: 1=B2C fizička osoba, 2=B2B poslovni subjekt, 3=B2G država/javna nabava, 4=EU, 5=INT ostatak svijeta
kupac_nazivNoNaziv kupca — OBAVEZNO za tip_kupca 2 (B2B) i 3 (B2G)
kupac_adresaNoAdresa kupca
kupac_oibNoOIB kupca — OBAVEZNO za tip_kupca 2 (B2B) i 3 (B2G)
uslugeYesStavke računa (najmanje jedna)
nacin_placanjaNoNačin plaćanja: 1=transakcijski račun, 2=gotovina, 3=kartice, 4=ček, 5=ostalo. Zadano 1.
rok_placanjaNoRok plaćanja u ISO 8601 formatu (YYYY-MM-DD)
datum_isporukeNoDatum isporuke u ISO 8601 formatu (YYYY-MM-DD)
napomeneNoNapomene na računu
jezik_racunaNoJezik računa: 1=hrvatski (zadano), 2=engleski, 3=njemački, 4=francuski, 5=talijanski, 6=španjolski
valuta_racunaNoValuta računa: 14=EUR (zadano), 12=USD, 11=GBP, 10=CHF, ...
tecajNoTečaj prema EUR (EUR=1), do 6 decimala
ibanNoOdabir računa za uplatu: 1 ili 2 (iz Solo postavki)
statusNoStatus računa: 1=otvoren (zadano), 2=poslan, 3=opomenut, 5=plaćen
Behavior4/5

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

Discloses automatic number assignment, fiscalization, and return values (number, amounts, ZKI/JIR, PDF link). Without annotations, it covers key behaviors but omits side effects or error conditions.

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?

Concise, no wasted words. Front-loaded with purpose, then automatic behaviors, return values, and special requirements. All sentences are substantive.

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?

Covers purpose, key behaviors, return values, and conditional constraints. With no output schema, description adequately explains what is returned. Could mention more about parameter combinations (e.g., when tip_racuna matters), but sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by consolidating conditional requirements (B2B/B2G: kupac_naziv, kupac_oib, kpd) into a single sentence, aiding understanding beyond individual parameter descriptions.

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?

Description clearly states the tool creates an invoice via Solo service, with automatic numbering and fiscalization. It distinguishes from sibling tools (get, list, next number) by being the only creation tool.

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?

Implies use for creating invoices, and includes specific requirements for B2B/B2G customers. Lacks explicit exclusion of siblings, but context is clear enough.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Seyn-Labs/mcp-ai-fiskalizacija'

If you have feedback or need assistance with the MCP directory API, please join our Discord server