largefile
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LARGEFILE_BACKUP_DIR | No | Backup directory path | ~/.largefile/backups |
| LARGEFILE_FUZZY_THRESHOLD | No | Match sensitivity (0.0-1.0) | 0.8 |
| LARGEFILE_MMAP_THRESHOLD_MB | No | Memory mapping limit in MB | 500 |
| LARGEFILE_MAX_SEARCH_RESULTS | No | Results per search | 20 |
| LARGEFILE_MEMORY_THRESHOLD_MB | No | RAM loading limit in MB | 50 |
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 |
|---|---|
| get_overviewA | Get file structure, size, and semantic outline for large files (code, logs, data). |
| search_contentA | Search large files for text patterns without loading entire content into memory. |
| read_contentA | Read specific portions of large files efficiently. |
| read_enclosingA | Find the enclosing function or class for a specific line number. Given a file and line number, returns the complete enclosing definition (function, method, class, struct, etc.) containing that line. Use depth=2 to get the parent definition (e.g., the class containing a method). Falls back to a centered context window for unsupported languages or top-level code. |
| edit_contentA | Edit large files using search/replace with fuzzy matching. |
| revert_editA | Restore a file to a previous state from automatic backups. |
| list_directoryA | List the contents of a directory. |
| search_directoryA | Search for a text pattern across all files in a directory. |
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 8 tools
Each tool has a clearly distinct purpose: editing, overview, reading, searching, listing, reverting, and structural analysis. No two tools overlap in functionality, making it easy for an agent to select the correct one.
All tools follow a consistent verb_noun pattern in snake_case (e.g., edit_content, get_overview, list_directory), with no mixed conventions or vague names.
8 tools is well-scoped for the domain of handling large files. Each tool addresses a specific need (reading, searching, editing, reverting, etc.) without unnecessary extras.
The tool set covers core operations for large files: overview, reading, searching, editing, reverting, and directory listing. Minor gaps like missing file creation or deletion are acceptable given the server's focus on large, existing files.