compare-mcp
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 |
|---|---|
| compare_modelsA | List all configured providers with their enabled status, type, and model. Does not expose API keys. |
| compare_runA | Fan out a code review to all enabled providers (or a subset) in parallel. Args: code: The source code to review. issue: Description of the bug or task. providers: Optional list of provider names to query. Defaults to all enabled. |
| compare_diffA | Diff provider responses: extract unique vs shared insights using fuzzy matching. Args: responses: Output from compare_run. |
| compare_debateC | Run a debate round where each model critiques others' findings, then synthesize. Args: responses: Output from compare_run. rounds: Number of debate rounds (default 1). |
| compare_todosB | Write ranked findings to the SQLite todo store. Args: findings: List of {title, description, severity, source_providers}. code_file: Optional file path the findings relate to. |
| compare_statusA | Return current todos grouped by status (pending, in_progress, done). Args: code_file: Optional filter by file path. |
| compare_todo_updateB | Update a todo's status. Args: todo_id: The todo ID to update. status: New status — one of 'pending', 'in_progress', 'done'. |
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 7 tools
Each tool has a clear, distinct purpose: running comparisons, diffing results, debating, listing models, and managing todos. No overlap or ambiguity.
All tools share the 'compare_' prefix and follow a verb_noun pattern (e.g., compare_run, compare_diff). The only minor deviation is 'compare_todo_update' which includes an extra verb, but it remains readable.
With 7 tools, the server is well-scoped for its purpose: running comparisons, analyzing results, and managing follow-up tasks. Neither too few nor excessive.
The core workflow (run comparison, analyze results, manage todos) is covered. Minor gaps exist, such as no tool to retrieve all results or delete todos, but agents can work around this.