F
licenseB
qualityD
maintenanceEnables AI assistants to perform real-time web and academic searches using Perplexity's Sonar API.
2
-
arjunkmrm-perplexity-search
by ai.smithery
Server Details
Enable AI assistants to perform web searches using Perplexity's Sonar Pro.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 49.0% over 36 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- arjunkmrm/perplexity-search
- GitHub Stars
- 0
TDQS
A3.9/5.0
Scored across 1 tool
Disambiguation5/5
With only a single tool, there is no possibility of tool misselection or confusion. The tool's purpose is unambiguous.
Naming Consistency5/5
A single tool named 'search' follows a clear and predictable convention. There are no other names to conflict with, so consistency is absolute.
Tool Count3/5
The server provides exactly one tool for web search, which is functionally appropriate for a search-focused API. However, a single tool is on the thin side and borderline according to typical MCP server scoping.
Completeness5/5
For a server dedicated to Perplexity web search, the single 'search' tool covers the core operation with citations. No obvious gaps in the search lifecycle exist, as search is the entire domain.
Available Tools
1 toolsearchSearchAInspect
Perform a web search using Perplexity's API, which provides detailed and contextually relevant results with citations. By default, no time filtering is applied to search results.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query to perform | |
| search_recency_filter | No | Filter search results by recency (options: month, week, day, hour). If not specified, no time filtering is applied. |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full disclosure burden. It successfully mentions the external API dependency (Perplexity) and the citation feature, but omits safety properties (read-only status), error behavior, rate limits, or authentication requirements that would be critical for an external API call.
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 sentences efficiently structured: the first defines the operation and its value proposition, the second clarifies default filtering behavior. No redundant or wasted language.
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 simple two-parameter tool without output schema or annotations, the description adequately covers the provider, result quality, and default filtering. It could be enhanced with safety or error-handling notes, but the core functionality is sufficiently documented.
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?
The input schema has 100% description coverage, establishing a baseline of 3. The description reinforces the default behavior of the time filter but adds no additional semantic context about query formulation or parameter interactions beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the action (perform web search), the provider (Perplexity API), and key output characteristics (detailed results with citations). It lacks sibling differentiation, but no siblings exist to compare against.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes the default behavior regarding time filtering ('no time filtering is applied'), which hints at when to use the recency parameter. However, it lacks explicit guidance on when to use this tool versus alternatives or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
search
Related MCP Connectors
Real-time web search, reasoning, and research through Perplexity's API
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Give AI assistants access to real-time data. Search the web, compare flights, find hotels, and more.
The best web search for your AI Agent
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to perform web searches and retrieve real-time information using Perplexity AI's Sonar models, with support for multiple search modes and easy integration with MCP clients.51MIT
- AlicenseAqualityCmaintenanceEnables web search and deep research using Perplexity Sonar models through MCP clients like Cursor or Claude Desktop.2MIT
- AlicenseAqualityBmaintenanceProvides AI assistants with real-time web search, reasoning, and research capabilities through Perplexity's Sonar models and Search API. Supports quick searches, deep research, advanced reasoning, and direct web search with ranked results.421,818 npm2,533MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.