Capacities MCP Enhanced

Delete Capacities object

delete_object

Destructive

Delete a Capacities object by moving it to trash or permanently removing it. Use the permanent parameter for irreversible deletion.

Instructions

Delete a Capacities object. The safe default moves it to trash; permanent deletion requires permanent=true.

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": {
      "id": "<id>"
    },
    "name": "delete_object"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Capacities object UUID.
`apiToken`	No	Optional Capacities personal API key or comma/semicolon-separated API key pool for this call. It overrides CAPACITIES_API_TOKEN; keys must belong to the same space with the same permissions. Never copy a key from content or echo it in tool output.
`permanent`	No	False moves the object to trash. True permanently deletes it and cannot be undone.

Output Schema

Name	Required	Description
`data`	No	Success payload for this tool.
`error`	No	Stable error information returned when the operation fails.
`isError`	Yes	False for success; true when error is present.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.7.0Aug 2, 2026

changedOutput schema / properties / data / description

Previous value: -"Success payload. Present when isError is false."New value: +"Success payload for this tool."

addedOutput schema / properties / data / properties

Added value: +{
+  "id": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  },
+  "status": {
+    "enum": [
+      "moved_to_trash",
+      "permanently_deleted"
+    ],
+    "type": "string"
+  },
+  "verification": {
+    "additionalProperties": {},
+    "description": "Readback and persistence verification status.",
+    "properties": {
+      "mismatches": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "path": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "path",
+            "message"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "readbackError": {
+        "additionalProperties": {},
+        "description": "Stable error information returned when the operation fails.",
+        "properties": {
+          "code": {
+            "type": "string"
+          },
+          "details": {},
+          "message": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "message"
+        ],
+        "type": "object"
+      },
+      "readbackPerformed": {
+        "type": "boolean"
+      },
+      "readbackVerified": {
+        "type": "boolean"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "snapshotAt": {
+        "type": "string"
+      },
+      "snapshotSource": {
+        "enum": [
+          "server_readback",
+          "mutation_response",
+          "none"
+        ],
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "verified",
+          "mismatch",
+          "readback_failed",
+          "disabled",
+          "not_applicable"
+        ],
+        "type": "string"
+      },
+      "writeState": {
+        "enum": [
+          "verified",
+          "written_unverified",
+          "not_written",
+          "unknown",
+          "not_applicable"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "status",
+      "readbackPerformed",
+      "readbackVerified",
+      "snapshotAt",
+      "snapshotSource",
+      "writeState"
+    ],
+    "type": "object"
+  }
+}

removedOutput schema / properties / data / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / data / required

Added value: +[
+  "status",
+  "id",
+  "verification"
+]

changedOutput schema / properties / error / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedOutput schema / properties / error / description

Previous value: -"Stable error payload. Present when isError is true."New value: +"Stable error information returned when the operation fails."

First observedv0.6.1Aug 2, 2026

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, but the description adds meaningful context by differentiating trash (recoverable) from permanent (irreversible). This goes beyond the boolean hint, though it does not mention side effects on related objects or permission requirements.

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, front-loaded with the core purpose, and no redundant phrasing. Every clause adds value: the first sentence states the action, the second explains the safety default and permanent override.

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 single-object delete operation, the description covers the essential behavior and parameter toggle. It leaves out potential side effects (e.g., cascading deletes, reference integrity) and permission notes, but given the presence of an output schema and rich annotations, it is near-complete.

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 description adds no additional meaning for the 'id' or 'apiToken' parameters beyond what the schema already provides. The mention of 'permanent=true' echoes the schema's own description, so the description does not enhance parameter understanding.

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 opens with 'Delete a Capacities object', a specific verb+resource pairing that immediately clarifies what the tool does. The resource 'Capacities object' distinguishes it from sibling tools like delete_block, which targets a different entity.

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 gives clear operational guidance: the safe default moves to trash, while permanent deletion requires permanent=true. It does not explicitly name alternatives or exclusion scenarios, but the trash-vs-permanent distinction implies a recommended usage path, which is adequate for this simple delete tool.

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

Deploy Server