mcp-tldr
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TLDR_BIN | No | Path to the tldr CLI binary if not in PATH |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tldr_treeA | Show file tree of a project directory. Use instead of ls/find. |
| tldr_structureB | Show code structure (classes, functions, imports) for a project. Use instead of reading files to understand structure. |
| tldr_contextA | Get LLM-ready context for a function/class. Use INSTEAD of reading large files. Returns only relevant code. |
| tldr_searchB | Search files for a pattern. Faster than grep for structural searches. |
| tldr_impactA | Find all callers of a function (reverse call graph). Use to understand what breaks if you change a function. |
| tldr_callsA | Build cross-file call graph starting from a function. |
| tldr_semanticA | Semantic code search using natural language. Use for conceptual searches like 'authentication logic' or 'payment handling'. |
| tldr_archB | Detect architectural layers from call patterns. Shows high-level architecture of the project. |
| tldr_warmA | Pre-build call graph cache for faster queries. Run once per project before using other tldr tools. |
| tldr_extractA | Extract full file analysis (classes, functions, methods, imports). Use to deeply understand a single file. |
| tldr_cfgB | Control flow graph for a function. Shows branches, loops, and execution paths. |
| tldr_dfgB | Data flow graph for a function. Shows how data moves through variables and expressions. |
| tldr_sliceA | Program slice: find all lines that affect a specific line. Use to understand what influences a value or statement. |
| tldr_deadC | Find unreachable (dead) code in a project. Useful for cleanup and refactoring. |
| tldr_importsC | Parse imports from a source file. Shows all dependencies of a file. |
| tldr_importersB | Find all files that import a module (reverse import lookup). Use to understand module usage across the project. |
| tldr_change_impactA | Find tests affected by changed files. Use before committing to know what to test. |
| tldr_diagnosticsC | Get type-check and lint diagnostics for a file or project. Use to find errors without running the code. |
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 18 tools
Each tool has a clearly distinct and well-defined purpose, from architecture detection to semantic search. There is no overlap or ambiguity; even related tools like tldr_calls and tldr_impact are differentiated by directionality.
All tools follow a consistent pattern: the prefix 'tldr_' followed by a snake_case name (e.g., tldr_change_impact). The naming convention is uniform and predictable.
With 18 tools, the server covers a broad range of static analysis features without being overwhelming. Each tool serves a specific purpose, and the count is well-suited for a comprehensive code understanding toolset.
The tool set is remarkably thorough, covering file tree, structure, imports, call graphs, control and data flow, diagnostics, search, dead code, and more. There are no obvious gaps for the domain of code analysis and comprehension.