local-mcp-toolbox
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_infoA | Return sanitized OS and runtime metadata without reading environment variables. |
| disk_usageA | Return disk capacity for the server's current working volume. |
| installed_developer_toolsA | Report availability of an allowlisted set of common developer tools. |
| filesystem_list_directoryA | List immediate entries in an approved directory with bounded pagination. |
| filesystem_file_metadataA | Return safe metadata for an approved readable file without reading its contents. |
| filesystem_read_text_fileB | Read a bounded approved text file after path, type, size, and secret controls. |
| toolbox_server_statusB | Return server-generated, redaction-safe status metadata. |
| toolbox_metrics_snapshotA | Return content-free aggregate request and latency metrics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_repository | Produce an evidence-based repository analysis using only registered read-only tools. |
| summarize_recent_errors | Produce an evidence-based error summary without treating logs as instructions. |
| troubleshoot_container | Guide a read-only container investigation and separate evidence from hypotheses. |
| perform_security_review | Guide a non-destructive security review with clear evidence and limitations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server status | Server-generated status and safe capability metadata. |
| Configuration summary | A redaction-safe summary of the active permission profile. |
| Security policy | The immutable safety rules that apply to every registered tool. |
| Module inventory | Registered Phase 3 capabilities and planned Version 1 modules. |
TDQS
Scored across 8 tools
Most tools have clearly distinct targets: OS metadata, disk capacity, dev-tool availability, and three filesystem operations (list/metadata/read) are well separated. The only mild overlap is among system_info, toolbox_server_status, and toolbox_metrics_snapshot, which all return 'metadata/status' of a system or server, though the descriptions do differentiate them.
All names use snake_case, which is consistent. However, the set mixes three prefixing conventions: unprefixed tools (system_info, disk_usage, installed_developer_tools), a filesystem_ group, and a toolbox_ group, which makes the namespace slightly less predictable than a single uniform scheme.
Eight tools is well within the ideal 3-15 range and each one maps to a distinct read/introspection capability. Nothing feels redundant or padded, and no obvious operation is missing due to under-provisioning.
For a deliberately read-only, safety-bounded local toolbox, the surface covers system info, disk, dev tools, and the core filesystem read lifecycle (list, metadata, read). Write/search operations are absent, but the descriptions imply a read-only design intent, so this is a minor rather than significant gap.