Skip to main content
Glama

perplexity_chat_completion

Run search-augmented chat completions using Perplexity AI to get grounded answers with web citations.

Instructions

Run a search-augmented chat completion with Perplexity AI. Returns grounded answers with citations from the web.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoPerplexity API key
modelNoModel (default: sonar). Options: sonar, sonar-pro, sonar-reasoning
promptNoUser message (alternative to messages)
system_promptNo
messagesNoJSON array of {role, content} messages
max_tokensNo
temperatureNo
search_recency_filterNoLimit sources by time: month, week, day, hour
search_domain_filterNoJSON array of domains to restrict search to
return_citationsNoInclude citation URLs in response (default true)
return_related_questionsNo
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It discloses that the tool performs web search and returns citations, which is helpful. However, it does not mention permissions, rate limits, or whether it is read-only.

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

Conciseness4/5

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

The description is very concise at two sentences, efficiently conveying the core purpose. However, it could benefit from a more structured format to list key features.

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

Completeness2/5

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

With 11 parameters and no output schema, the short description does not adequately cover the tool's complexity. It fails to explain parameter use cases or response structure beyond 'citations.'

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

Parameters2/5

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

Schema description coverage is 64%, and the description adds no additional meaning beyond what is in the schema. It does not elaborate on parameters like prompt vs messages, search filters, or output options.

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?

The description clearly states 'Run a search-augmented chat completion' with Perplexity AI, specifying the verb and resource. It distinguishes from other chat completion tools by highlighting 'grounded answers with citations from the web.'

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like openai_chat_completion or anthropic_create_message. It does not mention prerequisites (e.g., API key) or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'

If you have feedback or need assistance with the MCP directory API, please join our Discord server