Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_grok47

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

Instructions

Grok 4.7 — xAI's most advanced 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_grok47"
  }
}

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.0
Behavior2/5

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

With no annotations, the description must carry the full burden. It discloses only a cost (1 pro search query), which is genuinely useful, but says nothing about whether it performs web search, whether results are cited, latency, or how conversation_id affects state.

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-loads the model identity, but the brevity is under-specification rather than efficiency; the space saved is spent on marketing rather than on the parameter or usage facts 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 values need not be described. Still, for a 3-parameter tool with zero schema coverage and no annotations, the definition leaves source_focus and conversation_id entirely opaque and gives no basis for choosing this model over its many siblings.

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%, so the description must compensate — and it adds nothing about query, source_focus (notably its 'web' default and other valid values, which are undocumented), or conversation_id and its null default. An agent must guess at all three.

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 description only restates the tool's name ('Grok 4.7') plus a marketing claim ('xAI's most advanced model'). It never says what the tool actually does — answer a query, run a search, generate text — nor how it differs from siblings like pplx_sonar, pplx_ask, or pplx_grok47_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 when-to-use or when-not-to-use guidance. The 'COSTS 1 PRO SEARCH QUERY' note hints that cost should factor into selection, but no alternative or condition is named, so an agent cannot route between this and the ~30 sibling model tools.

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