Skip to main content
Glama

Remove an Autopilot search

removeAutopilotSearch
DestructiveIdempotent

Removes one saved Autopilot search by searchId from readAutopilot. Only when the candidate asked for it.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "searchId": "<searchId>"
    },
    "name": "removeAutopilotSearch"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchIdYesThe search's searchId from readAutopilot.

Output Schema

NameRequiredDescriptionDefault
statusYes
searchesYes
nextRunAtYes
tailorDocumentsYes
reviewBeforeSubmitYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds that exactly one search is deleted and that inputs/results are logged for usage tracking and support. It stops short of saying whether deletion is reversible or requires confirmation, which is the one behavioral detail an agent would still want.

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 core action and its consent constraint are front-loaded in one tight sentence. The second sentence is boilerplate privacy/telemetry disclosure that adds little for tool selection, though it is short enough not to obscure the main instruction.

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

Completeness5/5

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

For a single-parameter destructive tool, everything needed is present: what it does, which ID to supply and where it comes from, when it is appropriate, and a disclosure about data recording. Return values are covered by the output schema and the safety semantics by annotations, so nothing critical is missing.

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?

Schema coverage is 100% and the single searchId parameter is already documented in the schema, including its UUID format and its origin in readAutopilot. The description restates that provenance without adding any new meaning, so the baseline of 3 applies.

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 states a specific verb and resource ('Removes one saved Autopilot search'), scopes it to a single object by 'searchId', and points to the originating source ('from readAutopilot'). This distinguishes it cleanly from the add/edit siblings that operate on the same Autopilot search collection.

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?

It gives an explicit gating condition: 'Only when the candidate asked for it', which tells the agent not to invoke it unprompted. It does not name alternatives (e.g. editing rather than deleting a search), so the routing guidance is clear but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources