Skip to main content
Glama
Seyn-Labs

mcp-ai-fiskalizacija

by Seyn-Labs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SOLO_API_TOKENYesSolo API token — found in Settings after logging in to solo.com.hr

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
solo_create_invoiceA

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.

solo_get_invoiceA

Dohvaća pojedinačni račun sa solo.com.hr po njegovom ID-u (heksadecimalni identifikator, ne broj računa). Vraća sve detalje računa uključujući stavke, iznose, ZKI/JIR i PDF link.

solo_list_invoicesA

Dohvaća popis računa sa solo.com.hr (najnoviji prvi, do 1000 po stranici). Vraća broj računa, datum, bruto iznos i status za svaki račun.

solo_next_invoice_numberA

Dohvaća zadnji izdani račun sa solo.com.hr i izračunava sljedeći broj računa (redni broj + 1, format 'broj-poslovniProstor-uređaj', resetira se svake godine). Korisno za najavu broja prije izrade računa — napomena: Solo pri izradi računa sam dodjeljuje broj, pa ovaj alat služi za informaciju i provjeru.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: create, get by ID, list, and retrieve next invoice number. There is no overlap in functionality.

Naming Consistency4/5

All tools use the 'solo_' prefix and snake_case, but 'solo_next_invoice_number' is a noun phrase rather than a verb+noun pattern, introducing a minor inconsistency.

Tool Count4/5

4 tools cover the core operations for an invoice management server (create, read, list, and a utility). The count is reasonable, though slightly small for a full lifecycle.

Completeness3/5

The tool set provides create, get, list, and next number, but lacks update and delete/cancel functionality, which are notable gaps for invoice management.

Maintenance

ActivitySlowing
ResponsivenessSyncing