local-tools-mcp-server
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 |
|---|---|
| localtools_search_files | Search for files in a local directory by name pattern and/or extension. Supports recursive subdirectory search with configurable depth. Returns matching file paths with size and modification time. Args:
Examples:
Security:
|
| localtools_system_infoA | Retrieve basic system information including OS, CPU, memory, uptime, and user details. Useful for understanding the environment the AI is running in. All information is read-only and comes from the Node.js os module. Args:
Returns:
|
| localtools_list_directory | List files and folders in a directory with size, modification time, and type information. Supports pagination and optional hidden file inclusion. Results are sorted: directories first, then files. Args:
Returns: For JSON: { total, count, offset, entries: [{name, type, size, size_formatted, modified}], has_more, next_offset } |
| localtools_get_file_info | Get detailed metadata about a file or directory, including size, modification time, creation time, permissions, and type. Also returns a small preview of text-based files (up to 1000 bytes). Args:
Returns: For JSON: { path, type, size, size_formatted, created, modified, accessed, permissions, is_readable, is_writable, ...preview } Security:
|
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 1 tool
With only one tool, there is no ambiguity. The tool's purpose is clearly defined.
Single tool name is consistent with itself, using a clear snake_case pattern. No inconsistency to evaluate.
The server name 'local-tools-mcp-server' implies multiple tools, but only one is provided. This feels thin for the apparent scope.
The single tool covers basic system info, but the domain of 'local tools' is much broader. Obvious gaps exist (e.g., file operations, process management).