arjunkmrm-perplexity-search
Server Details
Enable AI assistants to perform web searches using Perplexity's Sonar Pro.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- arjunkmrm/perplexity-search
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.6/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as performing web searches with Perplexity's API, making it distinct by default.
A single tool named 'search' follows a simple, clear verb pattern. There are no other tools to compare against, so consistency is inherently perfect with no deviations or mixed conventions.
A single tool for a search-focused server feels too minimal for typical agent workflows. While it covers the core search functionality, the scope is thin, lacking complementary tools like filtering, result refinement, or citation management that would enhance coherence.
The server's domain appears to be web search, but with only a basic search tool, there are significant gaps. Missing operations include time filtering (mentioned as default-off but not controllable), result pagination, citation extraction, or query refinement, limiting agent effectiveness.
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.
| 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. |
Tool Definition Quality
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.
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.
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.
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.
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.
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!