MergeLoop
OfficialServer 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 |
|---|---|
| mergeloop_runA | Run one or more local model CLIs in single or council mode, capture outputs, identify disagreements, and return a synthesis-ready bundle. |
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 in the set, there is no possibility of confusing it with another. The single tool's purpose is clear and distinct simply because it is the only entry point.
The single tool name follows a clear server_action pattern ('mergeloop_run'). With only one tool, there are no internal inconsistencies or mixed conventions to confuse the naming scheme.
One tool for this narrow orchestration workflow is borderline but workable. However, the tool bundles multiple responsibilities (running, capturing, detecting disagreements, bundling) that could benefit from being split into smaller, more granular tools.
The tool covers the core workflow of running local model CLIs and producing a synthesis-ready bundle. Minor gaps exist around inspecting past runs or customizing the synthesis process, but these are acceptable given the tight scope.