Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gpt61_sol_thinking

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

Instructions

GPT-6.1 Sol Thinking — OpenAI's versatile model with thinking. 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_gpt61_sol_thinking"
  }
}

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.3/5.0
Behavior2/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. It usefully discloses that the tool costs one Pro Search query and that it uses a thinking model, but it does not explain whether it performs web search, how conversation state works, or any authentication or rate-limit behavior.

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 short, front-loaded with the model identity, and ends with a clear cost warning. The first clause largely repeats the tool name, but there is no bloated or redundant prose.

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 a model-selection tool with multiple siblings, three undocumented parameters, and no annotations, the description is materially incomplete. The output schema covers return values, but the definition still lacks input semantics and selection guidance.

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 mentions none of them. In particular, it provides no meaning for source_focus or conversation_id, leaving the agent to infer their behavior from names and defaults alone.

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 model as OpenAI's GPT-6.1 Sol in thinking mode and calls it versatile, which gives some sense of the resource. However, it never states the action the tool performs (for example, answering or researching a query), and it does not meaningfully distinguish this from sibling pplx_gpt61_sol beyond the word 'thinking'.

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?

There is no guidance on when to use this model versus pplx_gpt61_sol, other thinking models, or pplx_ask. The cost note implies a budget consideration but does not say when that cost is justified or when to choose an alternative.

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