Skip to main content
Glama
Perplexity Web MCP

Perplexity Web MCP

by jacob-bd

pplx_kimi_k3

Kimi K3 — Moonshot's newest model with thinking always enabled. COSTS 1 PRO SEARCH QUERY.

Instructions

Kimi K3 — Moonshot's newest model with thinking always enabled. 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_kimi_k3"
  }
}

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

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

With no annotations, the description does carry some behavioral burden and discloses two useful traits: thinking is always enabled, and each call costs one Pro Search query. However, it omits other relevant behavior such as what kind of search or answer is produced, how conversation state is handled, and any limits or prerequisites.

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?

The definition is short and front-loaded with the model identity and cost. It contains little filler, though the model-name restatement is somewhat redundant and the brevity comes at the expense of essential usage information.

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 the description still lacks the core action, parameter meanings, and selection guidance. For a three-parameter model-invocation tool with zero schema description coverage, this leaves too much for the agent to infer.

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%, so the description must compensate, but it says nothing about any of the three parameters. It does not explain the required query input, what source_focus controls or that it defaults to web, or what conversation_id is for.

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 restates the model name and adds marketing/model details ('Moonshot's newest model with thinking always enabled'), but never states the action the tool performs. It does not say whether this tool queries the model, runs a search, or returns an answer, so an agent cannot distinguish its operation from siblings without inferring from the name.

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 when-to-use guidance, no comparison to sibling model tools, and no exclusions. The cost note ('COSTS 1 PRO SEARCH QUERY') gives a budget consideration but does not explain when this model should be selected over alternatives.

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