Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gpt61_sol

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

Instructions

GPT-6.1 Sol — OpenAI's versatile 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_gpt61_sol"
  }
}

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

D1.8/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 burden, yet it discloses only that a call costs 1 Pro Search query. It says nothing about latency, whether conversation_id enables multi-turn context, what source_focus controls, or what kind of answer comes back; the output schema covers return shape but not behavior. The cost disclosure is genuine added value, which keeps this above the floor.

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

Conciseness3/5

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

Two short clauses with no padding and the model name front-loaded, so nothing is wasted structurally. However, the brevity is under-specification rather than efficiency: the space saved is not reallocated to the usage or parameter information an agent needs.

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?

With a required query parameter, an undocumented source_focus enum-like string, a nullable conversation_id, and no annotations, this definition is far too thin; the output schema spares it from explaining return values, but everything about invocation semantics is missing. An agent could call it with a bare query, but would have no basis for setting source_focus or conversation_id correctly.

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%, with three parameters (query, source_focus, conversation_id) documented nowhere. The description adds no meaning to any of them — not what source_focus values mean, not how conversation_id chains turns — leaving the agent to guess from bare property names and defaults.

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 names the model ('GPT-6.1 Sol — OpenAI's versatile model') but never states the verb or resource: it doesn't say it answers a query, generates text, or searches. 'Versatile model' is marketing framing rather than a description of what invoking the tool does, so an agent must infer its function from the parameter name 'query' and the sibling catalog.

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

Usage Guidelines1/5

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

There is no guidance on when to choose this model over the many sibling variants (pplx_gpt61_sol_thinking, pplx_claude_opus, pplx_query, pplx_smart_query, etc.), nor any exclusion or prerequisite. The only selection-relevant signal is the cost note, which tells an agent the price but not the appropriate use case.

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