tr-eli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TR_ELI_BASE_URL | No | Base URL for the Bedesten API | |
| TR_ELI_AUDIT_DIR | No | Directory for audit logs | |
| TR_ELI_CACHE_DIR | No | Directory for caching |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tr_search_legislationA | Search Turkish legislation by title and/or full text. |
| tr_get_legislation_contentA | Fetch the full text of a Turkish legislative document by its mevzuat_id. |
| tr_get_legislation_tocA | Fetch the article tree (madde agaci / table of contents) of a document. |
| tr_coverageA | Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns:
|
| tr_list_legislation_typesA | Enumerate all Turkish legislation types with live document counts. Returns:
|
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 targets a distinct aspect of Turkish legislation: searching, listing types, fetching full text, fetching table of contents, and declaring coverage gaps. There is no meaningful overlap; even get_legislation_content and get_legislation_toc are clearly separated by the type of content returned.
Most tools follow a consistent tr_<verb>_<object> pattern (tr_search_legislation, tr_list_legislation_types, tr_get_legislation_content, tr_get_legislation_toc). The lone exception is tr_coverage, which uses a noun instead of a verb, creating a minor but noticeable deviation.
Five tools is well-scoped for a legal research connector: two for discovery, two for retrieval, and one for coverage metadata. Each tool serves a clear purpose and none feel redundant or extraneous.
The surface covers the core workflow of searching, enumerating types, fetching full text, and navigating structure via TOC, plus a dedicated gap-awareness tool. For a read-only legislation domain, this is complete; there are no obvious missing operations that would block typical agent workflows.