Skip to main content
Glama
jacob-bd

Perplexity Web MCP

by jacob-bd

pplx_gpt54_thinking

Perform deep reasoning with extended thinking on complex queries. Each answer uses one Pro Search query.

Instructions

GPT-5.4 Thinking — OpenAI's versatile model with extended thinking. COSTS 1 PRO SEARCH QUERY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
source_focusNoweb
conversation_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description only discloses that using this tool costs 1 PRO SEARCH QUERY. It does not mention other behaviors like idempotency, safety, required permissions, or the nature of 'extended thinking'. The cost disclosure is helpful but insufficient.

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 very concise with two sentences, front-loading the model name and cost. However, its brevity sacrifices necessary detail for completeness, but within the constraint of minimalism it is well-structured.

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

Completeness2/5

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

Given the existence of many sibling tools with similar names (e.g., pplx_gpt54, pplx_gpt55_thinking), the description fails to differentiate effectively. It does not explain what 'extended thinking' entails, nor does it reference the output schema (which exists but is not shown). Parameter and behavioral gaps make it incomplete for reliable tool selection.

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

Parameters1/5

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

Schema description coverage is 0%, meaning no parameter descriptions exist in the schema. The description does not mention any parameters (query, source_focus, conversation_id), leaving their purpose and usage completely unclear. This is a critical gap.

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

Purpose3/5

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

The description states it's OpenAI's versatile model with extended thinking, indicating it generates responses using a 'thinking' variant. However, it does not specify the action (e.g., generate, respond) and only weakly distinguishes from siblings like pplx_gpt54 or pplx_gpt55_thinking by name and 'thinking' label.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as pplx_gpt54 (without thinking) or pplx_gpt55_thinking. The description lacks any comparison or selection criteria, leaving the agent without decision support.

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