devbench
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileA | 讀取專案內的一個檔案並回傳內容（附行號）。 |
| list_filesA | 依照 glob 樣式列出專案內的檔案。 |
| run_testsA | 在專案內執行 pytest 並回傳結果摘要。 |
| git_logA | 查看專案最近的 git commit 紀錄。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| code_review | 用固定的檢查清單審查某個檔案 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 專案摘要 | 這個專案的檔案數、程式碼行數與目錄結構概觀 |
TDQS
Scored across 4 tools
Each tool performs a distinct operation: listing files, running tests, viewing git history, and reading file contents. There is no overlap or ambiguity between any pair of tools.
The verb_noun pattern is mostly consistent (list_files, run_tests, read_file), but git_log deviates slightly as it reads more like a noun compound than a verb phrase. Overall, naming is clear and predictable.
Four tools is a well-scoped set for a development inspection environment. Each tool serves a clear purpose without redundancy, and the count feels neither too thin nor bloated.
The tool set covers the core read-only workflows: enumerating, reading, testing, and version tracking. Missing write/edit capabilities could be a gap in some augmentation contexts, but for a benchmark or inspection tool, this surface is mostly sufficient.