Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Delete agent

delete_agent

DestructiveIdempotent

Permanently remove an AI agent and its persistent disk. Workflows are paused, not deleted, and remain assignable to another agent.

Instructions

Permanently delete an agent and revoke its disk. This cannot be undone. Workflows the agent built are NOT deleted — they belong to the account — but the ones that were live are paused, and none of them run again until you assign them to another agent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent's UUID to delete.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes	The successful HTTP status code from the underlying operation.
`workflows_paused`	No	How many workflows this agent had built and had running were paused by the deletion. They are not deleted: assign them to another agent to run them again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "status": {
+      "description": "The successful HTTP status code from the underlying operation.",
+      "type": "integer"
+    },
+    "workflows_paused": {
+      "description": "How many workflows this agent had built and had running were paused by the deletion. They are not deleted: assign them to another agent to run them again.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Even though annotations already mark the tool as destructive and idempotent, the description adds significant behavioral context: deletion is permanent, disk is revoked, workflows are NOT deleted but are paused and will not run until reassigned. This goes well beyond the annotations and clarifies partial data preservation.

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 with no filler. The core action and irreversibility are front-loaded, and the workflow-related caveat is presented in a clear second sentence. Every sentence earns its place.

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 destructive tool with one parameter, the description fully covers the necessary context: irreversibility, disk revocation, workflow ownership, and runtime behavior of affected workflows. The output schema exists so return-value details are not required.

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 description coverage is 100% and the single parameter agent_id is already documented as 'The agent's UUID to delete.' The description adds no additional meaning beyond the schema, so the baseline score 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: 'Permanently delete an agent and revoke its disk.' This clearly distinguishes the tool from siblings like create_agent, get_agent, and list_agents, and its scope is unambiguous.

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 provides clear context by explaining the consequences of deletion, especially how workflows are preserved but paused. It implies the alternative of assigning workflows to another agent, though it does not explicitly name set_workflow_agent or state when not to use this tool.

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