AI Dev Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_repo_readerA | Recursively reads all source files in a local repository directory. Automatically ignores |
| code_executorA | Executes a small Python or Node.js code snippet in a sandboxed child process. Hard limits: 15 second timeout, 64 KB output cap. The snippet runs in an isolated temp file — no persistent state between calls. Ideal for quick calculations, data transformations, and API-free logic. |
| doc_searchB | Searches all documents in a local |
| terminal_commanderA | Executes a safe Windows CMD or PowerShell command on the local machine. Protected by a strict allowlist — only pre-approved commands are permitted. Dangerous patterns (rm -rf, del /s, format, shutdown, registry edits, etc.) are blocked even if the base command is allowed. Allowed commands include: dir, git, node, npm, python, tsc, docker, ipconfig, and more. Use this to run |
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 has a clearly distinct purpose with no overlap: code_executor runs code snippets, doc_search searches documents, github_repo_reader reads repository files, and terminal_commander executes system commands. The descriptions make it easy to differentiate between them, as they target different resources and use cases.
The naming follows a consistent snake_case pattern with descriptive names (e.g., code_executor, doc_search), but there is a minor deviation with github_repo_reader using a compound term that could be more aligned (e.g., repo_reader). Overall, the naming is readable and mostly predictable.
With 4 tools, the count is well-scoped for an AI Dev Assistant, covering key development tasks like code execution, documentation search, repository reading, and terminal commands. Each tool earns its place without feeling excessive or insufficient for the server's purpose.
The tool set covers essential development workflows, including code execution, documentation, repository management, and system operations. A minor gap exists in not having tools for more advanced tasks like debugging or version control beyond basic commands, but agents can work around this with the provided tools.