Tokenectomy-Razor
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_error_contextC | Extracts detailed source code context and git diff from an error log |
| search_stack_overflowB | Search Stack Overflow for a specific error query |
| apply_code_patchA | Applies a code patch to a specific file by replacing original_code with new_code. |
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 3 tools
Each tool has a clearly distinct role: extracting error context, searching for solutions, and applying a patch. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case: get_error_context, search_stack_overflow, apply_code_patch. No naming deviations.
Three tools form a tight, well-scoped workflow for handling and fixing errors. Neither too thin nor excessive for the stated purpose.
The core loop of retrieve context → search for solution → apply fix is covered. A minor gap is lack of a post-patch verification step, but the surface is functional.