tugra
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MULTI_AKIS | No | Fallback for TUGRA_AKIS when TUGRA_AKIS and TALAMUS_AKIS are unset. | |
| MULTI_KASA | No | Fallback for TUGRA_KASA when TUGRA_KASA and TALAMUS_KASA are unset. | |
| TUGRA_AKIS | No | Path to the telemetry directory. If unset, the server looks next to the installed package. TALAMUS_AKIS and MULTI_AKIS are accepted as fallback variable names. | |
| TUGRA_KASA | No | Path to the vault directory containing markdown facts. If unset, the server looks next to the installed package. TALAMUS_KASA and MULTI_KASA are accepted as fallback variable names. | |
| MULTI_YETKI | No | Fallback for TUGRA_YETKI when TUGRA_YETKI and TALAMUS_YETKI are unset. | |
| TUGRA_YETKI | No | Path to the authorization store directory for shared-vault setups. If unset or empty, single-user mode is enabled. TALAMUS_YETKI and MULTI_YETKI are accepted as fallback variable names. | |
| TALAMUS_AKIS | No | Fallback for TUGRA_AKIS when TUGRA_AKIS is unset. | |
| TALAMUS_KASA | No | Fallback for TUGRA_KASA when TUGRA_KASA is unset. | |
| TALAMUS_YETKI | No | Fallback for TUGRA_YETKI when TUGRA_YETKI is unset. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fact_searchB | Search stored facts. Retired and rotten facts are omitted unless archive is true. Rank: token score, then freshness, then confidence. Boundary facts add a no-claim warning. Authorization required. |
| fact_readA | Read one fact by uid. Body passes through the presentation layer (injection escaping). Retired facts include superseded_by and the reason. |
| fact_proposeA | Write a draft fact under kasa/_oneriler/ (or quarantine). Secret patterns are rejected before any write; the matching text is never returned. type=boundary is always quarantined. Fake mcp:// sources are not injected. |
| event_reportB | Append a telemetry line to akis/YYYY-MM-DD.jsonl. No network. |
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 4 tools
Each tool targets a distinct operation: searching facts, reading by UID, proposing a draft fact, and appending telemetry. There is no meaningful overlap between fact_search, fact_read, fact_propose, and event_report.
All tool names use lowercase snake_case and an object-first pattern (fact_search, fact_read, fact_propose, event_report). Although event_report lacks the fact_ prefix, it follows the same noun-verb shape, making the naming predictable and consistent.
Four tools is a well-scoped surface for a fact-store server: two retrieval paths, one proposal/write path, and one telemetry path. Each tool earns its place without redundancy or bloat.
The search/read/propose set covers the main fact consumption and contribution workflows. Direct lifecycle operations such as update, retire, or approve are absent, but the proposal mechanism and archive flag suggest a curated interface where this is an acceptable minor gap.