LangLa Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANGLA_DOCS_DIR | Yes | Path to the docs directory containing protocol documentation files (e.g. CLIENT_*.md, SERVER_*.md, AUDIT_*.md). |
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 |
|---|---|
| server_overviewC | Tóm tắt cổng, quy tắc wire, thứ tự docs ưu tiên cho agent sửa client LangLa. |
| list_docsB | Liệt kê file markdown protocol trong docs/ (CLIENT_*, SERVER_*, AUDIT_*). |
| read_docB | Đọc toàn bộ một file docs (vd. CLIENT_STATS_LONG.md hoặc CLIENT_STATS_LONG). |
| search_docsA | Tìm chuỗi trong toàn bộ docs (MSG, tên field, triệu chứng). |
| get_msgB | Tra nhanh tài liệu theo số MSG (vd. 62, 63, -49, -88, -79). |
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 access pattern: listing files, reading a whole file, searching free text, and looking up a specific MSG number. read_doc and get_msg overlap slightly since both return document content, but get_msg is clearly scoped to MSG-numbered entries, so an agent can choose reliably.
Four of five tools follow a clean verb_noun pattern (read_doc, list_docs, search_docs, get_msg). server_overview breaks the pattern by being noun-only, a minor but noticeable deviation.
Five tools is well-scoped for a documentation-retrieval server, with each tool covering a distinct lookup strategy. No redundant or filler tools.
The surface covers the core docs workflow: overview, listing, full read, free-text search, and targeted MSG lookup. Minor gaps exist, such as no way to enumerate all MSG entries or page through very large documents, but agents can work around these via search_docs.