Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gpt6_astra

GPT-6 Astra — OpenAI's most capable model. COSTS 1 PRO SEARCH QUERY. Requires Max subscription.

Instructions

GPT-6 Astra — OpenAI's most capable model. COSTS 1 PRO SEARCH QUERY. Requires Max subscription.

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

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.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does contribute two real facts: the per-call cost in pro search queries and the Max subscription requirement. It says nothing about whether the call is a safe read, how long it takes, or how conversation_id affects state, so meaningful gaps remain.

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?

Two short clauses, with the model identity and the two hard constraints front-loaded and no filler. The brevity is efficient rather than padded, though it comes at the cost of omitting what the tool actually does.

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, but for a three-parameter model-invocation tool the definition omits the operation itself and all parameter meaning. Cost and subscription requirements are covered, but that is not enough for an agent to call it correctly without guessing.

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 (query, source_focus, conversation_id with default null), so the description is the only place semantics could be supplied — and it supplies none. Neither source_focus's meaning/enum-like values nor how conversation_id continues a thread is explained anywhere.

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 which model this is (GPT-6 Astra, OpenAI's most capable) and thereby distinguishes it from the many sibling model tools, but it never states the action: there is no verb or resource saying that it answers a query with this model. An agent can infer the family convention from siblings like pplx_ask, but the definition itself only names a model.

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

Usage Guidelines3/5

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

Useful selection signals are present: 'most capable model' implies hard problems, 'COSTS 1 PRO SEARCH QUERY' flags a budget tradeoff, and 'Requires Max subscription' is a hard prerequisite. However, there is no explicit when-to-use versus the obvious alternatives such as pplx_gpt6_astra_thinking or pplx_gpt61_sol, and no exclusions.

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