Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_claude_fable52_think

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

Instructions

Claude Fable 5.2 Thinking — Anthropic's most capable model with extended thinking. 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_think"
  }
}

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.5/5.0
Behavior3/5

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

With no annotations, the description carries full disclosure duty, and it does add two genuinely useful facts: the per-call cost (1 Pro search query) and the Max-subscription requirement. Beyond that it discloses nothing about whether the model performs web search, how the conversation context is used, or latency/thinking-time expectations. The cost and auth disclosures lift it above baseline but leave major behavioral gaps for an unannotated tool.

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?

Two short sentences, front-loaded with the model identity and followed by the operational constraints. There is no filler, though the em-dash model blurb is arguably redundant with the tool name.

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 fairly excused, but the definition is still thin for a tool with three undocumented parameters, no annotations, and many near-identical siblings. It gives cost and auth but omits the tool's actual function and any routing guidance, leaving an agent unable to confidently choose this over the other Claude variants.

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% across three parameters (query, source_focus, conversation_id) and the description adds no meaning to any of them. It never explains what source_focus controls, what values it accepts beyond the default "web," or how conversation_id resumes a thread. For a 0%-coverage schema this is a serious omission.

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 Thinking — Anthropic's most capable model with extended thinking"), which distinguishes it somewhat from the sonnet/opus siblings by capability tier. However, it never states the operation the tool performs — no verb like "answer" or "query" — so an agent must infer from the name that it submits a prompt to this model. It reads more as a model label than a description of an action.

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?

The only guidance is a cost gate ("COSTS 1 PRO SEARCH QUERY") and an auth prerequisite ("Requires Max subscription"). There is no indication of when to choose this model over pplx_claude_opus_think, pplx_claude_sonnet_think, or the non-thinking variants, nor any when-not-to-use condition, despite roughly twenty sibling model tools.

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