Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gemini4_carbon

Gemini 4 Carbon — Google's most powerful model. COSTS 1 PRO SEARCH QUERY. Requires Max subscription.

Instructions

Gemini 4 Carbon — Google's most powerful 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_gemini4_carbon"
  }
}

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 carries the full burden, and it does add genuinely useful operational facts: it consumes 1 Pro Search Query and requires a Max subscription, which affects both cost and eligibility. It says nothing about return behavior, latency, or what conversation_id enables (multi-turn state), leaving significant behavioral gaps for a tool with zero annotation coverage.

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 tight sentences with the model identity up front and the cost/auth constraints capitalized for salience. Nothing is wasted, though the brevity is partly under-specification rather than discipline.

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 tool with no annotations and 0% schema coverage the description should explain source_focus and conversation_id semantics and differentiate it from the near-identically named _thinking sibling. Cost and subscription are covered; parameter and tool-selection behavior are not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. Only 'query' is weakly implied by the fact that this is a model tool; 'source_focus' (default "web", allowed values unstated) and 'conversation_id' (null default, entirely unexplained) get no meaning from either field.

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 names the underlying resource ("Gemini 4 Carbon — Google's most powerful model") but supplies no verb describing what invoking the tool actually does — presumably answering a query — and does not distinguish it from the sibling pplx_gemini4_carbon_thinking or the many other model tools. An agent can infer it is a model-backed query tool, but only from the name and sibling list, not from the description itself.

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 a gating note ("Requires Max subscription") and a cost note, but no guidance on when to pick this model over pplx_gemini4_carbon_thinking, pplx_gemini4_hydrogen, pplx_query, or pplx_sonar. No mention of task types the model suits or exclusions.

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