Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_grok47_thinking

Grok 4.7 Thinking — xAI's most advanced model with thinking. COSTS 1 PRO SEARCH QUERY.

Instructions

Grok 4.7 Thinking — xAI's most advanced 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_grok47_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.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden, and it does disclose one genuinely useful trait: the cost of one Pro Search query. However, it says nothing about latency, thinking-token verbosity, whether conversation_id threads context, or any permission constraints, so important behavior is left implicit.

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?

It is short and front-loaded with the model identity and cost, which is good. But the brevity is under-specification rather than economy — the space saved is not spent on the usage or parameter guidance 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?

An output schema exists, so return format need not be explained, but the tool has three undocumented parameters and sits among a dozen near-identical model siblings with no routing criteria. For that complexity, the definition leaves too much for the agent to guess.

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% and the description does not mention any of the three parameters. The meaning of source_focus and conversation_id in particular is entirely undocumented anywhere, so the description fails to compensate for the schema gap.

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 ('Grok 4.7 Thinking — xAI's most advanced model with thinking') but never states the tool's action or resource — that it answers a query — and gives no explicit differentiation from the sibling pplx_grok47 non-thinking variant. The model name is a label, not a verb, so the agent must infer the purpose.

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 when-to-use or when-not-to-use guidance relative to the many sibling model tools (pplx_grok47, pplx_gpt61_sol_thinking, pplx_sonar, etc.). The only routing signal is the cost note, which implies 'use sparingly' but never names an alternative or a selection condition.

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