Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_council

Model Council — query multiple models in parallel, get synthesized consensus.

Instructions

Model Council — query multiple models in parallel, get synthesized consensus.

IMPORTANT — BEFORE calling this tool, you MUST:

  1. Tell the user the available models: sonar, gpt61_sol, gpt6_astra, gemini4_carbon, gemini4_hydrogen, gemini_pro, claude_sonnet, claude_opus, claude_opus55, claude_fable52, grok47, nemotron, glm53, kimi_k3

  2. Check pplx_usage() first. If Subscription is Pro, do not include Max-only models: gpt6_astra, gemini4_carbon, claude_opus, claude_opus55, claude_fable52

  3. Ask the user WHICH models they want in their council and HOW MANY

  4. Inform them of the cost: each council model = 1 Pro Search query, plus synthesis (default chairman sonar = Sonar 2 pass — still counts as a normal query toward limits)

  5. Get explicit confirmation before executing

Default council: GPT-6.1 Sol, Claude Sonnet 5.5, Gemini 4 Hydrogen (Pro-compatible, 3 diverse providers).

Args: query: The question to ask all council models source_focus: Source type for all models (none/web/academic/social/finance/all or connector source ID) models: Comma-separated model names to use as council members. Available: sonar, gpt61_sol, gpt6_astra, gemini4_carbon, gemini4_hydrogen, gemini_pro, claude_sonnet, claude_opus, claude_opus55, claude_fable52, grok47, nemotron, glm53, kimi_k3. Default: "gpt61_sol,claude_sonnet,gemini4_hydrogen" (3 models + synthesis = 4 Pro Searches) Max-only: gpt6_astra, gemini4_carbon, claude_opus, claude_opus55, claude_fable52. Exclude these when pplx_usage shows a Pro subscription. synthesize: Whether to synthesize a consensus from all responses. Set false to get only individual responses (saves 1 Sonar 2 call). thinking: Enable extended thinking for council models (gpt61_sol, gpt6_astra, gemini4_carbon, gemini4_hydrogen, claude_sonnet, claude_opus, claude_opus55, claude_fable52, and grok47 support toggle; glm53 and kimi_k3 are always thinking). chairman: Model to use for synthesis (default: "sonar" / Sonar 2). Non-sonar chairmen cost 1 extra Pro Search query.

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": "pplx_council"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
modelsNogpt61_sol,claude_sonnet,gemini4_hydrogen
chairmanNosonar
thinkingNo
synthesizeNo
source_focusNoweb

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.17.0
    • changedInput schema / properties / chairman / enum
      Previous value: -[
      -  "auto",
      -  "sonar",
      -  "deep_research",
      -  "gpt56_terra",
      -  "gpt56_sol",
      -  "gpt6_sol",
      -  "grok45",
      -  "grok47",
      -  "claude_sonnet",
      -  "claude_opus",
      -  "claude_opus55",
      -  "gemini_pro",
      -  "gemini38",
      -  "nemotron",
      -  "glm52",
      -  "glm53",
      -  "kimi_k26",
      -  "kimi_k3"
      -]New value: +[
      +  "auto",
      +  "sonar",
      +  "deep_research",
      +  "gpt61_sol",
      +  "gpt6_astra",
      +  "gemini4_carbon",
      +  "gemini4_hydrogen",
      +  "gemini_pro",
      +  "claude_sonnet",
      +  "claude_opus",
      +  "claude_opus55",
      +  "claude_fable52",
      +  "grok47",
      +  "nemotron",
      +  "glm53",
      +  "kimi_k3"
      +]
    • changedInput schema / properties / models / default
      Previous value: -"gpt56_terra,claude_sonnet,gemini_pro"New value: +"gpt61_sol,claude_sonnet,gemini4_hydrogen"
  2. Changed1 schema field changedv0.16.0
    • changedInput schema / properties / chairman / enum
      Previous value: -[
      -  "auto",
      -  "sonar",
      -  "deep_research",
      -  "gpt56_terra",
      -  "gpt56_sol",
      -  "grok45",
      -  "claude_sonnet",
      -  "claude_opus",
      -  "gemini_pro",
      -  "nemotron",
      -  "glm52",
      -  "kimi_k26"
      -]New value: +[
      +  "auto",
      +  "sonar",
      +  "deep_research",
      +  "gpt56_terra",
      +  "gpt56_sol",
      +  "gpt6_sol",
      +  "grok45",
      +  "grok47",
      +  "claude_sonnet",
      +  "claude_opus",
      +  "claude_opus55",
      +  "gemini_pro",
      +  "gemini38",
      +  "nemotron",
      +  "glm52",
      +  "glm53",
      +  "kimi_k26",
      +  "kimi_k3"
      +]
  3. Changed2 schema fields changedv0.14.7
    • changedInput schema / properties / chairman / enum
      Previous value: -[
      -  "auto",
      -  "sonar",
      -  "deep_research",
      -  "gpt54",
      -  "gpt55",
      -  "claude_sonnet",
      -  "claude_opus",
      -  "gemini_pro",
      -  "nemotron",
      -  "glm52",
      -  "kimi_k26"
      -]New value: +[
      +  "auto",
      +  "sonar",
      +  "deep_research",
      +  "gpt56_terra",
      +  "gpt56_sol",
      +  "grok45",
      +  "claude_sonnet",
      +  "claude_opus",
      +  "gemini_pro",
      +  "nemotron",
      +  "glm52",
      +  "kimi_k26"
      +]
    • changedInput schema / properties / models / default
      Previous value: -"gpt54,claude_sonnet,gemini_pro"New value: +"gpt56_terra,claude_sonnet,gemini_pro"
  4. First observedv0.14.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it quantifies cost (each council model = 1 Pro Search query, synthesis adds one, non-sonar chairman costs an extra query), and specifies that synthesize=false saves a Sonar 2 call. It also discloses a tier-based model restriction tied to subscription status, which an agent could not infer from the schema.

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?

Front-loaded with the purpose, then a numbered procedure, then per-argument notes — a structure an agent can follow. It loses a point for repetition: the full 14-model roster appears in step 1 and again under `models`, and the Max-only exclusion list is stated twice.

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

Completeness5/5

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

An output schema exists, so return values need not be described. Covering cost accounting, subscription gating, defaults, and a required confirmation workflow is ample for a 6-parameter tool with one required argument.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does for all six parameters: source_focus enumerates values (none/web/academic/social/finance/all or connector source ID), models lists valid names with a default and Max-only exclusions, thinking names which models support the toggle and which are always-on, and chairman gives the default plus cost implication. This adds substantial meaning beyond the bare JSON schema.

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?

Opens with a specific verb and resource ('query multiple models in parallel, get synthesized consensus'), which cleanly separates it from single-model siblings like pplx_ask, pplx_query, and pplx_smart_query. The concept of a 'council' plus synthesis is unambiguous without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit pre-call checklist: query pplx_usage first, exclude Max-only models on Pro subscriptions, ask the user which models and how many, disclose cost, and obtain confirmation. It also states the default council and why it was chosen (Pro-compatible, 3 diverse providers). Both when-to-use and prerequisite conditions are spelled out.

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