Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_gemini4_hydrogen

Gemini 4 Hydrogen — Google's latest model. COSTS 1 PRO SEARCH QUERY.

Instructions

Gemini 4 Hydrogen — Google's latest 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_gemini4_hydrogen"
  }
}

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 carries the full burden, and it discloses only the cost dimension, which is genuinely useful. It says nothing about latency, whether the model retains state via conversation_id, whether it performs live web search, or any limits on invocation.

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 cost constraint, so nothing is wasted. However, the brevity comes at the expense of substance rather than reflecting a well-packed definition.

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 explained, but with zero annotations and zero parameter documentation the definition is too thin for a three-parameter model-invocation tool. The agent lacks the information needed to choose this tool or fill its optional parameters correctly.

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?

Three parameters exist at 0% schema description coverage, and the description explains none of them. The meanings of source_focus (default 'web') and conversation_id (stateful follow-up vs. fresh call) are entirely undocumented, and the required query parameter is unelaborated.

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 identifies a model ('Gemini 4 Hydrogen — Google's latest model') and a cost, but never states a verb or resource: it does not say it answers queries, performs search, or generates text. An agent cannot distinguish its function from siblings like pplx_gemini4_hydrogen_thinking or pplx_gemini4_carbon based on this text alone.

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?

The only selection signal is the cost note ('COSTS 1 PRO SEARCH QUERY'), which implies this is a premium call but gives no when-to-use or when-not-to-use guidance. Nothing routes the agent between this, the thinking variant, or the many other model siblings.

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