Skip to main content
Glama
jacob-bd

Perplexity Web MCP

by jacob-bd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

pplx_query

Query Perplexity AI with a specific model or thinking mode when automatic routing cannot meet your needs; each call costs one Pro Search query.

Instructions

Query Perplexity AI with explicit model selection. COSTS 1 PRO SEARCH QUERY per call.

Prefer pplx_smart_query for automatic quota-aware routing. Use this only when you need a specific model or thinking mode. Omitted model, thinking, and source_focus fall back to saved defaults (set with pwm config in the CLI), then to auto/web/off.

Args: query: The question to ask model: Model to use - 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 (any live catalog identifier is also accepted). An unknown name returns an error with close-match suggestions. thinking: Enable extended thinking mode (available for gpt56_terra, gpt56_sol, gpt6_sol, grok45, grok47, claude_sonnet, claude_opus, claude_opus55, gemini38, kimi_k26; always on for gemini_pro, nemotron, glm52, glm53, and kimi_k3) source_focus: Source type - none (model only, no search), web, academic, social, finance, all, or connector source ID from pplx_connectors() files: Local file paths to attach (PDF or image). On Free-tier accounts an attachment can make the query count as a Pro Search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNo
modelNo
queryYes
thinkingNo
source_focusNo
conversation_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.16.0
    • addedInput schema / properties / files
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / model / anyOf
      Added value: +[
+  {
+    "enum": [
+      "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"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / model / default
      Previous value: -"auto"New value: +null
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "auto",
-  "sonar",
-  "deep_research",
-  "gpt56_terra",
-  "gpt56_sol",
-  "grok45",
-  "claude_sonnet",
-  "claude_opus",
-  "gemini_pro",
-  "nemotron",
-  "glm52",
-  "kimi_k26"
-]
    • removedInput schema / properties / model / type
      Removed value: -"string"
    • addedInput schema / properties / source_focus / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / source_focus / default
      Previous value: -"web"New value: +null
    • removedInput schema / properties / source_focus / type
      Removed value: -"string"
    • addedInput schema / properties / thinking / anyOf
      Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / thinking / default
      Previous value: -falseNew value: +null
    • removedInput schema / properties / thinking / type
      Removed value: -"boolean"
  2. Changed1 schema field changedv0.14.7
    • changedInput schema / properties / model / 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"
+]
  3. First observedv0.14.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses per-call cost ('COSTS 1 PRO SEARCH QUERY'), that Free-tier attachments can upgrade a query to Pro Search, that omitted params fall back to saved defaults then auto/web/off, and that unknown model names return an error with close-match suggestions. It omits auth/permission requirements, but cost, defaults, and error behavior are strong disclosures beyond 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 purpose and the cost warning before routing guidance and the arg list. The Args block is long but each line carries information not present in the schema, so it is justified rather than padding.

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?

An output schema exists, so return values need not be described. For a 6-param tool the description covers cost, routing, defaults, error behavior, and most parameters; the only missing piece is any meaning for conversation_id.

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

Parameters4/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 largely does: model enum values are annotated with which ones support thinking, source_focus options are explained semantically ('none (model only, no search), web, academic...'), and files notes accepted types and tier effects. conversation_id, however, is left entirely undocumented, which is the one gap.

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?

States a specific verb and resource ('Query Perplexity AI') plus the differentiating scope ('with explicit model selection'). It explicitly separates itself from pplx_smart_query, so an agent can choose between them without opening either 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 alternative ('Prefer pplx_smart_query for automatic quota-aware routing') and the precise condition that selects this tool instead ('only when you need a specific model or thinking mode'). When-to-use and when-not-to-use are both covered.

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

Deploy Server

Other Tools