Skip to main content
Glama
jacob-bd

Perplexity Web MCP

by jacob-bd

pplx_council

Query multiple AI models simultaneously and receive a synthesized consensus answer. Combine diverse model perspectives for comprehensive, balanced results.

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, gpt56_terra, gpt56_sol, grok45, claude_sonnet, claude_opus, gemini_pro, nemotron, glm52, kimi_k26

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

  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-5.6 Terra, Claude Sonnet 5, Gemini 3.1 Pro (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, gpt56_terra, gpt56_sol, grok45, claude_sonnet, claude_opus, gemini_pro, nemotron, glm52, kimi_k26. Default: "gpt56_terra,claude_sonnet,gemini_pro" (3 models + synthesis = 4 Pro Searches) Max-only: gpt56_sol, claude_opus. 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 (gpt56_terra, gpt56_sol, grok45, claude_sonnet, claude_opus, kimi_k26 support toggle; gemini_pro, nemotron, and glm52 are always thinking). chairman: Model to use for synthesis (default: "sonar" / Sonar 2). Non-sonar chairmen cost 1 extra Pro Search query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
modelsNogpt56_terra,claude_sonnet,gemini_pro
chairmanNosonar
thinkingNo
synthesizeNo
source_focusNoweb

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses behavioral traits including cost (each council model = 1 Pro Search query, plus synthesis), model-specific thinking support, and chairman implications. It also explains that the chairman defaults to sonar and non-sonar chairmen cost extra, providing transparency beyond the bare structure.

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?

The description is well-structured with a title line, an 'IMPORTANT' section with bullet points, and an Args block. It is fairly concise for a complex tool, though slightly verbose. Front-loading purpose and prerequisites is good.

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?

The description fully covers all 6 parameters, usage scenario, costs, prerequisites, and model restrictions. Given the tool's complexity and many sibling tools, it is very complete and provides sufficient context for correct invocation.

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?

Despite 0% schema description coverage, the description's 'Args:' block explains each parameter (query, source_focus, models, synthesize, thinking, chairman) in detail, including meanings, defaults, available options, and behavioral implications. This adds significant value over the bare 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?

The description clearly states the tool's purpose as 'Model Council — query multiple models in parallel, get synthesized consensus.' It specifies the verb (query multiple models in parallel) and resource (council of models), and distinguishes from many single-model sibling tools like pplx_gpt56_terra and pplx_sonar.

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?

The description provides an 'IMPORTANT' section with step-by-step instructions before calling, including checking pplx_usage, asking user for models, informing cost, and getting confirmation. It also explains default council, subscription restrictions, and provides guidance on when to use alternatives.

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/jacob-bd/perplexity-web-mcp'

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