my-pi
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_infoB | Inspect the configured workspace. Read-only. |
| fs_statC | Stat a single path within the workspace. Read-only. |
| fs_readC | Read a single file within the workspace and obtain a content fingerprint/snapshot. Read-only. |
| fs_writeB | Write a single file within the workspace (stale-safe). Mutates exactly one file. |
| fs_patchC | Apply a hashline-style single-file patch (stale-safe). Mutates exactly one file. |
| searchC | Search the workspace (grep or glob). Read-only. |
| vcs_statusC | VCS status. Read-only. |
| vcs_diffD | VCS diff. Read-only. |
| ast_searchC | Structural AST search. Read-only. |
| lsp_statusC | Language server status. Read-only. |
| lsp_diagnosticsC | Language server diagnostics for a file. Read-only. |
| lsp_symbolsC | Symbols for a file. Read-only. |
| lsp_navigateC | Navigate (definition/references/hover) via language server. Read-only. |
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 13 tools
Each tool maps to a distinct resource/action: filesystem stat/read/write/patch, text vs structural search, VCS status/diff, and LSP status/diagnostics/symbols/navigate. Overlaps like fs_stat vs fs_read and search vs ast_search are resolved by clear descriptions.
All tools use snake_case, but suffixes mix nouns and verbs (workspace_info, vcs_status vs fs_read, ast_search, lsp_navigate). The prefix-based grouping is predictable, so mostly consistent with minor deviations.
13 tools is well-scoped for a workspace/code-intelligence server, covering file ops, search, VCS, and LSP without obvious redundancy. Each tool appears to earn its place.
Core read/write/patch/search/VCS/LSP workflows are covered, but there is no explicit delete/move/rename for files and VCS is limited to status/diff. These are minor gaps workable around for an inspection/editing agent.