Skip to main content
Glama

compare_models

Ask one question across 2–5 Perplexity models, then compare shared citations and agreeing or divergent facts in a consolidated Markdown report.

Instructions

Ask one question across 2–5 Perplexity models (running concurrently when multiple PERPLEXITY_PROFILE_DIRS profiles or backend='api' are configured), compare shared citations and agreed/divergent key facts, and return a consolidated Markdown report (spooled to .txt if >= 15000 chars or output_file is set).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "compare_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesQuestion or architecture/code comparison prompt to send to each model
modelsNoOptional list of 2-5 Perplexity models (defaults to GPT-6.1 Sol, Claude Sonnet 5.5, Gemini 4 Hydrogen).
backendNoExecution backend: 'auto' (uses official Perplexity Agent API if PERPLEXITY_API_KEY is configured and thread_url is omitted, otherwise browser Pro session), 'browser' (Playwright Pro UI), or 'api' (official HTTPS Agent API).
sourcesNoOptional source filter applied to every model in the comparison.
no_cacheNoIf true, bypasses the local response cache (default TTL 3600s, configurable via PERPLEXITY_CACHE_TTL_SECONDS) and forces a fresh search.
output_fileNoOptional .txt file path to save the full answer to (regardless of length). Relative paths resolve inside the server's outputs directory. When omitted, answers at or above 15000 chars (configurable via PERPLEXITY_LONG_OUTPUT_CHARS) are automatically saved to a .txt file with an inline preview and path.
verify_claimsNoIf true (or PERPLEXITY_VERIFY_CLAIMS=1), fetches cited pages and checks key facts (numbers, dates, versions, names) for each claim, marking supported / weak / unverified.
timeout_secondsNoOptional timeout in seconds for waiting on the answer (defaults to server timeout, 900s / 15 minutes; max 1800s for very large code or multi-part responses).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses concurrency conditions, the comparison semantics (shared citations, agreed vs divergent facts), the consolidated Markdown return format, and the 15000-char spool-to-.txt threshold. Gaps remain around failure behavior when one model errors and any session/auth prerequisites for the browser backend.

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

Conciseness4/5

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

It is a single sentence, but the purpose is front-loaded ('Ask one question across 2-5 Perplexity models') and each dependent clause adds real information about concurrency, aggregation, and output handling. The nested parentheticals make it dense to parse, which is the main cost.

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?

For an eight-parameter tool with no annotations and no output schema, the description covers the essentials: what gets compared, what shape the result takes, and when large output is diverted to a file. Missing pieces are error/partial-failure handling and backend authentication prerequisites, which an agent may need in practice.

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 description coverage is 100%, so all eight parameters are already documented in the schema, which sets the baseline at 3. The description only echoes the 2-5 model range and output_file spooling behavior without adding syntax or edge-case meaning beyond what the schema states.

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

Purpose4/5

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

The description gives a specific verb-and-resource pair: it fans one question out across 2-5 Perplexity models, compares shared citations and agreed/divergent facts, and returns a consolidated Markdown report. That is unmistakably distinct from the sibling search/search_advanced tools, though it never names those siblings to make the distinction explicit.

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?

Usage is implied rather than stated: an agent can infer this is the tool for cross-model consensus checking, and the description notes the concurrency precondition (multiple PERPLEXITY_PROFILE_DIRS profiles or backend='api'). There is no explicit when-not-to-use guidance or named alternative, so the agent must infer the routing decision.

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