Skip to main content
Glama
Sign In
perplexity-agent-mcp

perplexity-agent-mcp

by zalez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Cancel Perplexity Research

perplexity_agent_cancel
Destructive

Stop an active Perplexity research run by providing its response ID. Use this to halt ongoing research when it is no longer needed.

Instructions

Ask Perplexity to stop a research run that is no longer needed. Perplexity does not report usage for cancelled runs, so this cannot tell you whether it changed your bill.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "response_id": "<response_id>"
    },
    "name": "perplexity_agent_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_idYesThe response_id from perplexity_agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as destructive, and the description adds the behavioral nuance that Perplexity does not report usage for cancelled runs, so the billing impact is unknown. This goes beyond the structured annotation by explaining a consequence of the operation.

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 short sentences, front-loaded with the action and followed by a relevant caveat. No redundant phrasing.

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 one-parameter cancel operation, the description covers the action, the trigger condition, and a key side-effect caveat. It doesn't specify the return value, but no output schema exists and the behavior is sufficiently clear.

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 only parameter (response_id) is already fully described in the schema, so the description doesn't need to add more. It correctly references where the ID comes from, matching the schema.

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 uses a specific verb ('stop') and resource ('a research run') and clearly distinguishes from sibling tools (perplexity_agent, perplexity_agent_result) by focusing on cancellation. Title 'Cancel Perplexity Research' reinforces the action.

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

Usage Guidelines4/5

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

The description states when to use it ('when no longer needed'), giving clear contextual guidance. It does not explicitly name alternatives or exclusions, but the sibling tool names make alternative uses obvious.

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

Deploy Server

Other Tools