Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_nemotron

Nemotron 3.5 Super VL — NVIDIA's newest Nemotron model. COSTS 1 PRO SEARCH QUERY.

Instructions

Nemotron 3.5 Super VL — NVIDIA's newest Nemotron 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_nemotron"
  }
}

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

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only the billing characteristic ('COSTS 1 PRO SEARCH QUERY'), which is genuinely useful information not available elsewhere. It says nothing about whether this is a read-only query call, how conversation_id threads state, what the 'VL' vision capability implies given no image parameter exists, or what the tool returns. One real disclosure against several missing ones.

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 only two fragments, so nothing is padded, but the brevity is under-specification rather than discipline and the 'newest model' clause is pure marketing. The cost warning is well placed at the end where it will be read, but the description leads with branding instead of function.

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-value explanation is not required, and the cost disclosure covers billing. Everything else an agent needs is absent: the operation itself, the meaning of source_focus and conversation_id, and any differentiation from roughly two dozen sibling model tools. For a 3-parameter tool at 0% schema coverage with no annotations, this is materially under-described.

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), so the description must compensate and instead adds nothing. It never mentions any of the three names, explains no source_focus values despite a 'web' default that clearly implies alternatives, and gives no hint that conversation_id carries prior-turn context.

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 entry routes to ('Nemotron 3.5 Super VL — NVIDIA's newest Nemotron model'), which is the primary distinguishing factor among a large sibling set of model-named tools. But it never states the action: there is no verb saying it answers a query with that model, so an agent must infer the operation purely from the name and the parameter set. 'Newest' is marketing filler rather than a capability statement.

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?

No guidance on when to choose this model over the many sibling model tools (pplx_sonar, pplx_gpt61_sol, the claude/gemini/grok variants, or pplx_query/pplx_smart_query). The only selection signal offered is the cost note, which does imply a tradeoff but never states the condition under which paying that cost is worthwhile or when a cheaper model should be used instead.

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