semamerge
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_merge_safetyA | Quick pre-merge safety check. Analyzes two branches for semantic conflicts that Git would miss (signature changes, removed exports, parameter mismatches, etc.). Returns a risk score: safe/warning/danger. |
| analyze_branchesA | Deep semantic analysis between two branches. Returns a detailed per-file report of all semantic changes and conflicts, including cross-file dependency issues. |
| list_semantic_changesA | Lists all semantic changes on a branch (function additions/removals, export changes, type changes, etc.) relative to a base. Useful for understanding what semantically changed. |
| analyze_file_pairA | Deep-dive semantic diff of a single file between two branches. Shows exactly what each branch changed and where conflicts arise. |
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 targets a distinct analysis granularity: quick safety check, deep branch analysis, change listing, and single-file diff. The only minor overlap is between check_merge_safety and analyze_branches, but their quick-vs-detailed distinction is clear.
All tool names consistently follow a verb_noun pattern: check_merge_safety, analyze_branches, list_semantic_changes, analyze_file_pair. The naming style is uniform and predictable.
Four tools is well-scoped for a semantic merge analysis server. Each tool covers a distinct level of analysis without redundancy or unnecessary bloat.
The tools cover the full analysis workflow: quick safety triage, comprehensive branch-level analysis, semantic change listing, and per-file deep dives. No obvious gaps exist for the stated analysis-focused purpose.