Perplexity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| perplexity_searchC | Search the web using Perplexity AI |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose, making it impossible for an agent to misselect between multiple options.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'perplexity_search' follows a clear verb_noun format, but consistency cannot be assessed across a set of one.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a web search server, this minimal scope might suffice for basic queries, but it feels thin and lacks auxiliary operations like filtering or advanced search options.
The server's purpose appears to be web search, and the single tool covers the core action of searching. However, there are notable gaps, such as no tools for refining searches, handling different search types (e.g., news, images), or managing search history, which could lead to agent workarounds or limitations.