Skip to main content
Glama

set_default_model

Set or clear a sticky default Perplexity model that search tools use automatically when no model is specified. Persists locally so you avoid repeating the model choice on each call.

Instructions

Set or clear your sticky default Perplexity model (persisted locally). Used automatically by search/search_advanced whenever no model argument is passed.

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": {
      "model": "<model>"
    },
    "name": "set_default_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesModel name to set as default (e.g. 'GPT-6.1 Sol', 'Grok 4.7', 'Claude Sonnet 5.5', 'Best'), or 'none' to clear.
profileNoOptional browser profile name or directory path for isolated/concurrent execution (e.g. 'default', 'worker-2'). When omitted, automatically routes to an idle slot in PERPLEXITY_PROFILE_DIRS / default profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description does carry useful behavior: the setting is persisted locally and silently affects later search calls, and 'none' clears it. It does not say whether the model name is validated, whether login/auth is required, or what a successful call returns or overwrites, so the mutation's failure and side-effect profile is only partially disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the action and its persistence come first, the downstream consumption second. No filler, no repetition of the tool name, nothing that could be cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter setter with no output schema and no annotations, the description covers purpose, persistence, clearing behavior, and downstream effect. The remaining gaps (validation of model names, profile-slot side effects, return/confirmation) are minor for a simple preference write.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters (model, profile) are already documented with examples in the schema. The description's 'set or clear' phrasing restates the 'none' convention already present in the schema and adds no new syntax or constraints, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (set or clear) and resource (sticky default Perplexity model), plus the scope note that the value is persisted locally. An agent can immediately tell this is a configuration write, not a search, and the parenthetical clarifies the semantics of 'sticky'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Adds real context for when this matters: the default is consumed automatically by search/search_advanced when no model argument is passed, which tells the agent why and when to call it. It stops short of explicit exclusions or pointing at list_models for discovery, so it is clear but not fully routing.

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