Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gemini4_carbon_thinking

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

Instructions

Gemini 4 Carbon Thinking — Google's most powerful model with thinking. 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_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.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It does valuable work by disclosing that each call consumes 1 Pro Search Query and requires a Max subscription — real operational cost information an agent cannot get from the schema. However it says nothing about latency, whether thinking output is returned, or whether conversation_id implies stateful multi-turn behavior.

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 compact sentences with the model identity, cost, and access requirement front-loaded and no filler. It is terse to the point of being cryptic on purpose, but nothing is wasted.

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 no explanation. But for a 3-parameter tool with zero schema coverage and a large sibling family, the definition omits both the action performed and the meaning of two of its parameters, leaving the agent unable to invoke it confidently beyond passing a bare query string.

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% and the description explains none of the three parameters. `query` is self-evident, but `source_focus` (defaulting to 'web', with no listed allowed values) and `conversation_id` (stateful continuation?) are completely undocumented in both schema and description, leaving the agent guessing at valid values and semantics.

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 ('Gemini 4 Carbon Thinking — Google's most powerful model with thinking') and its cost, but never states the actual verb or resource — it does not say it answers a query, performs research, or returns a response. An agent can infer this is a model-backed query tool from the sibling family (pplx_gemini4_carbon, pplx_gemini4_hydrogen_thinking), but the definition itself never says what the tool does.

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 guidance on when to pick this model over its many siblings — no comparison to pplx_gemini4_carbon (non-thinking), pplx_gemini4_hydrogen_thinking, or the other thinking models. The only selection signal is a cost/subscription constraint, which is a constraint rather than a use case.

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