Llama-Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLAMA_BASE_URL | No | llama.cpp server URL | http://localhost:8080 |
| LLAMA_MODEL_NAME | No | Model identifier | local-model |
| LLAMA_REQUEST_TIMEOUT | No | Timeout in seconds | 120 |
| LLAMA_DEFAULT_MAX_TOKENS | No | Default token budget | 131072 |
| LLAMA_DEFAULT_TEMPERATURE | No | Default sampling temperature (string 'None' for server default) | None |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| implement_codeA | Generate implementation code from a specification. Use this tool when you need the local model to write a function, class, module, API endpoint, CRUD logic, glue code, or any other implementation artefact. Provide as much context and constraints as possible for the best results. IMPORTANT: Always review the returned code before accepting it. |
| generate_testsA | Generate test code for a given implementation. Produces a complete, runnable test file that covers happy paths and edge cases. Specify the testing framework and any particular scenarios you want covered. IMPORTANT: Always review the returned tests before accepting them. |
| refactor_codeA | Apply a specific refactoring to existing code. The local model will apply the requested transformation while preserving external API and behavior. Useful for mechanical refactors like renaming, extracting methods, converting patterns, etc. IMPORTANT: Always review the returned code before accepting it. |
| fix_codeA | Fix bugs in code based on errors or review feedback. Provide the broken code along with compiler/runtime errors and/or reviewer comments. The local model will return a corrected version that addresses all reported issues. IMPORTANT: Always review the returned fix before accepting it. |
| generate_docsA | Generate documentation for existing code. Produces documentation in the requested style — inline docstrings, README content, or structured API reference. IMPORTANT: Always review the returned documentation for accuracy. |
| check_local_model_healthA | Check if the local llama.cpp server is reachable and loaded. Returns availability status and model metadata. Call this before starting a batch of implementation tasks, or when a previous tool call failed with a connection error, to decide whether to retry or fall back to direct cloud-model implementation. |
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 6 tools
Each tool targets a distinct workflow: implementation, test generation, refactoring, bug fixing, documentation, and health checking. Descriptions clearly separate concerns, so an agent should be able to select the right tool without confusion.
Tool names follow a consistent verb_noun snake_case pattern: implement_code, generate_tests, check_local_model_health, refactor_code, fix_code, generate_docs. The naming convention is uniform and predictable.
Six tools is a well-scoped set for a local-model code-assistance bridge. Each tool earns its place, covering the main code-generation and modification workflows without redundant or unnecessary additions.
The toolset covers the core lifecycle of generating, testing, refactoring, fixing, and documenting code, plus a health check. A minor gap is the lack of a general code review or explanation tool, but agents can work around it with the existing tools.