Skip to main content
Glama

compare

Run the same content against multiple AI models in parallel to compare their responses. Supports multi-turn conversations with project context and file inclusion.

Instructions

Compare responses from multiple AI models. Runs the same content against all specified models in parallel. Supports multi-turn conversations with project context and file inclusion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesStep name (e.g., 'Initial Analysis', 'Security Review')
contentYesYour question to the AI Assistant. Provide detailed context: your goal, what you've tried, what worked, any specific challenges. IMPORTANT: Always include paths to relevant files in `relevant_files` - do NOT skip this step.
step_numberYesCurrent step
next_actionYesRecommended next action: 'continue' to proceed, 'stop' to end
base_pathYesAbsolute path to project root to id the project and load project files
thread_idNoThread ID to continue previous conversation and preserve context. WHEN TO USE: - None/omit: Starting a brand new review or chat session (step_number=1) - Provide thread_id: Continuing a multi-step workflow from a previous response (step_number>1) The thread_id is returned in every response - save it and reuse it for follow-up steps.
relevant_filesNoAbsolute paths of ALL files relevant to this question (up to 100 files). CRITICAL: For project-level questions (features, architecture, design), you MUST include project documentation (README.md, docs/, architecture diagrams). For code-specific questions, include the implementation files, related modules, tests, and configs. Example 1: 'What feature should we build?' → Include README.md, src/server.py, config/*.*, tests/. Example 2: 'Review this function' → Include the file with the function, related modules, tests, and documentation.
modelsNoList of LLM models to run in parallel (minimum 2) (will use default models (['gpt-4', 'gpt-3.5-turbo']) if not specified)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses parallel execution, multi-turn conversation support, and file inclusion. With no annotations, description provides good behavioral context, though no mention of side effects or permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, each adding essential information. No redundancy or filler. Front-loaded with core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and output schema exists, description covers key aspects. Could mention output format but not required. Adequate for a comparison tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 8 parameters with descriptions. Description adds that content is sent to all models in parallel, but this is implicit from the tool's purpose. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool compares responses from multiple AI models, running same content in parallel. Distinguishes from siblings like chat and codereview by emphasizing multi-model comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Does not explicitly specify when to use vs alternatives like debate or chat. Mentions multi-turn support but lacks guidance on choosing this tool over others.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/religa/multi_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server