Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_claude_sonnet_think

Claude Sonnet 5.5 Thinking — Anthropic's newest reasoning model. COSTS 1 PRO SEARCH QUERY.

Instructions

Claude Sonnet 5.5 Thinking — Anthropic's newest reasoning model. COSTS 1 PRO SEARCH QUERY.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
source_focusNoweb
conversation_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses only billing cost. It says nothing about reasoning-token behavior, latency, source scoping, conversation reuse, or what happens to a supplied conversation_id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but shortness here reflects under-specification rather than economy; the one sentence that exists is marketing framing plus a cost warning. The genuinely useful fact (cost) is buried after the model 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 values need not be explained, but that is the only burden lifted. For a zero-coverage three-parameter model-invocation tool with no annotations, the definition leaves almost everything an agent needs unanswered.

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, and the description never mentions query, source_focus, or conversation_id. With neither schema nor description explaining them, an agent has no basis for setting source_focus or deciding whether to pass conversation_id.

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

Purpose2/5

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

The text restates the model's identity ("Claude Sonnet 5.5 Thinking — Anthropic's newest reasoning model") rather than stating a verb and resource. Neither the name nor the description says the tool submits a query to that model, so an agent must infer the operation from the parameter schema.

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 decision-relevant cue is the cost note ("COSTS 1 PRO SEARCH QUERY"), which lets an agent weigh expense but not choose between this and the many sibling model tools. There is no when-to-use, when-not-to-use, or alternative named.

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