io.github.BerkantACUN/efatura-kontrol
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| belge_dogrulaA | UBL-TR belgesini denetler: XML biçimi, OASIS UBL 2.1 XSD, GİB e-Fatura şematronu (498 kural,
kod listeleri dahil), satır/vergi/tevkifat/dip toplam aritmetiği, imza yapısı. Her bulgu: kod,
seviye (hata/uyari/bilgi), GİB'in özgün mesajı, satır numarası, Türkçe açıklama ve düzeltme.
|
| belge_ozetiC | Belgenin kimliği: senaryo, fatura tipi, numara, UUID, tarih, para birimi, satıcı/alıcı (VKN/TCKN, unvan), satırlar (ilk 50), vergiler, dip toplamlar, imzalı mı. Summary of a UBL-TR document: parties, lines, taxes and totals. |
| bulgu_aciklaA | Bir bulgu kodunun (örn. sch-GeneralUnitCodeCheck-1, hesap-dip-odenecek) Türkçe açıklaması, hangi alanın neden reddedildiği ve nasıl düzeltileceği. Explains a finding code. |
| kod_listesiB | GİB kod listesinin değerleri (şematronun fiilen uyguladığı liste): UnitCodeList, TaxType,
InvoiceTypeCodeList, ProfileIDType, CurrencyCodeList, WithholdingTaxTypeWithPercent,
TaxExemptionReasonCodeType, PaymentMeansCodeTypeList... |
| kod_listeleriA | Mevcut GİB kod listelerinin adları ve Türkçe açıklamaları; kaynak paket sürümleri. Names of the available code lists and the GİB package versions this build uses. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: summarizing, validating, explaining findings, and accessing code lists. The two code list tools are clearly differentiated by singular/plural and value/name semantics. No two tools could be plausibly confused.
All names use lowercase snake_case and follow a resource-prefix pattern (belge_*, kod_*, bulgu_*). There is minor inconsistency in the suffix type: some are verbs (dogrula, acikla) and some are nouns (ozeti, listesi, listeleri), but the overall pattern remains predictable and readable.
Five tools is well-scoped for a focused e-invoice validation server. Each tool serves a clear need in the workflow of validating, understanding, and correcting UBL-TR documents, with no redundant or extraneous tools.
The tool set covers the full validation workflow: validate a document, get a summary, explain reported findings, and inspect the code lists used by the schematron. There are no obvious dead ends—the outputs of belge_dogrula feed directly into bulgu_acikla and kod_listesi lookups.