Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_claude_fable52

Claude Fable 5.2 — Anthropic's most capable model. COSTS 1 PRO SEARCH QUERY. Requires Max subscription.

Instructions

Claude Fable 5.2 — Anthropic's most capable model. COSTS 1 PRO SEARCH QUERY. Requires Max subscription.

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_claude_fable52"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
source_focusNoweb
conversation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two genuinely useful behavioral facts: each call consumes 1 pro search query and a Max subscription is required. It omits other important traits such as multi-turn behavior when conversation_id is supplied, latency, and any rate limits or failure modes.

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?

Three short, front-loaded fragments with no filler; the cost and auth constraints are prominent. The brevity is efficient but edges toward telegraphic, leaving the core action unstated.

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?

An output schema exists, so return-value explanation is not required, but for a tool with three undocumented parameters and a crowded sibling set the definition is thin. It never says what a call actually does with the query or how conversation threading behaves, leaving real gaps for an agent to guess at.

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

Parameters2/5

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

Schema description coverage is 0% across 3 parameters, so the description must compensate and it says nothing about any of them. 'query' is self-evident, but 'source_focus' (default 'web', presumably a source-selection knob) and 'conversation_id' (evidently a thread-continuation handle) are left entirely undefined.

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 identifies the underlying model ('Claude Fable 5.2 — Anthropic's most capable model') but never states the action the tool performs, i.e. that it sends a query to that model and returns a response. It gives no explicit differentiation from the many siblings (pplx_claude_opus, pplx_claude_sonnet, and their _think variants) beyond an unquantified 'most capable' claim.

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 when-to-use guidance is given: nothing says when to pick this over pplx_claude_opus, the _think sibling, or pplx_ask/pplx_query. The only selection-relevant signal is the cost and subscription note, which is ancillary rather than routing guidance.

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