Perplexity2 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for Perplexity2 API authentication |
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 |
|---|---|
| postD | Discover the power of data with our API, designed to search Google data effortlessly. Leverage AI to analyze and organize information, unlocking insights and enhancing your decision-making capabilities. |
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 with other tools. The single tool 'post' stands alone with a distinct purpose, eliminating any risk of misselection.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'post' follows a simple verb pattern, and no inconsistencies can exist in a set of one.
A single tool is too few for a server named 'Perplexity2 MCP Server' with a description focused on data discovery, AI analysis, and Google search. This suggests a broader scope that would typically require multiple tools (e.g., for search, analysis, organization), making the count inappropriate and likely incomplete.
The server's description implies capabilities like searching Google data, AI analysis, and organizing information, but only a generic 'post' tool is provided. This is severely incomplete, lacking specific tools for search, retrieval, analysis, or other core functions, which will cause agent failures in handling the intended domain.