re-patch
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_patchA | Return server status + version. Always |
| sha256_manifestA | Compute the SHA-256 manifest of path. Args: path: file to hash Returns:: Use this to record the canonical SHA-256 of the original
binary before any patch is applied. The hash is the
rollback key: |
| apply_patchA | Copy src to dst, then splice new_bytes_b64 at offset. This is the on-disk patch primitive. The original bytes at src are never modified; the patch is written to a copy at dst. The function returns both the pre-patch and post-patch SHA-256 so the analyst can record the patch's net effect in the report. Args: src: source file (the original; never modified) dst: destination file (created or overwritten with the patched copy) offset: byte offset into dst at which to write (0-based) new_bytes_b64: base64-encoded bytes to splice in confirm_legal: free-text justification (the audit trail; the server does not enforce policy) Returns:: Override-scope contract: this tool is gated behind
the run's policy override (see |
| restore_originalA | Copy original back to restore_target, optionally verifying the original's SHA-256 against expected_sha256 first. This is the rollback primitive. The function:
Args: original: file whose bytes are the canonical "original" (typically the source the patch was applied from) restore_target: file to write the original bytes to (typically the patched copy) expected_sha256: optional hex-encoded SHA-256 to verify original against confirm_legal: free-text justification (audit trail) Returns:: |
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 4 tools
Each tool has a distinct purpose: applying patches, health check, rollback, and hash computation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (apply_patch, check_patch, restore_original, sha256_manifest).
4 tools is well-scoped for a focused patching utility; each tool is necessary and justified.
Core patching workflow (hash, apply, rollback, health) is covered, though a tool to list applied patches is missing.