ulasim
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ULASIM_DB | No | Path to the DuckDB database file used by the MCP server. Defaults to data/ulasim.duckdb relative to the repository containing the server file. If the dbt build database location is overridden (ULASIM_DUCKDB_PATH), set ULASIM_DB to the same database file. | |
| ULASIM_SORGU_ZAMAN_ASIMI | No | Positive finite query timeout in seconds for the sorgu tool. Queries are interrupted after 30 seconds by default. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| semaA | Veriyi sorgulamadan önce marts tablo ve sütunlarını, kapsamı ve uyarıları öğrenin. |
| sorguC | Veri analizi için tek bir SELECT çalıştırın; sınırlı satır ve kesilme bilgisini alın. |
| istasyon_bulB | İstasyon adını veya yazım varyantını arayarak grup, kod, hat ve tarihleri bulun. |
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 3 tools
Each tool has a clearly distinct role: sema inspects schema metadata, sorgu executes a SELECT query, and istasyon_bul searches for a station by name. There is little risk of confusing these actions, even for an agent unfamiliar with the domain.
The names mix bare nouns (sema, sorgu) with a noun+verb compound (istasyon_bul), so there is no predictable verb_noun pattern across the set. They remain readable and domain-appropriate, but the convention is inconsistent.
Three tools is a lean but reasonable surface for a read-only transport data query server. Each tool covers a necessary step—schema discovery, query execution, and station lookup—though the set feels slightly minimal.
The tools cover the core read-only workflow: learn the schema, run a SELECT, and resolve station names. Minor gaps exist, such as no explicit table listing or richer result metadata, but these are workable through sema and sorgu.