Skip to main content
Glama
Nyrest

Capacities MCP Enhanced

by Nyrest
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

Delete Capacities block

delete_block
Destructive

Delete a Capacities block and its nested child blocks by providing the object and block IDs. Use after verifying content to avoid accidental removal.

Instructions

Delete one existing Capacities block by object ID and block ID. Nested child blocks are deleted with their parent; read structured content first and use only when the deletion is intentional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesCapacities object UUID.
blockIdYesUUID of the block to delete.
apiTokenNoOptional 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoSuccess payload for this tool.
errorNoStable error information returned when the operation fails.
isErrorYesFalse for success; true when error is present.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.7.0
    • 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: +{
+  "object": {
+    "additionalProperties": {},
+    "description": "Capacities API object returned by the server.",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "status": {
+    "const": "deleted",
+    "type": "string"
+  },
+  "verification": {
+    "additionalProperties": {},
+    "properties": {
+      "absent": {
+        "type": "boolean"
+      },
+      "blockId": {
+        "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"
+      },
+      "mismatches": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "code": {
+              "type": "string"
+            },
+            "message": {
+              "type": "string"
+            },
+            "path": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "code",
+            "path",
+            "message"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "propertyId": {
+        "type": "string"
+      },
+      "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",
+      "blockId",
+      "propertyId",
+      "absent"
+    ],
+    "type": "object"
+  }
+}
    • removedOutput schema / properties / data / propertyNames
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "status",
+  "object",
+  "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."
  2. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already include destructiveHint=true, but the description adds valuable context beyond that: nested child blocks are deleted with the parent, implying cascade deletion. It also adds a precautionary note to read structured content first. This enriches the behavioral model without contradicting annotations.

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?

The description is two sentences, front-loaded with the primary action, then a crucial caution about nested deletions. Every word earns its place, and there is no redundancy or filler. It is highly scannable and effective.

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?

Given that an output schema exists and the annotations cover the destructive nature, the description provides sufficient context for a delete tool. It explains the core action, the cascade deletion behavior, and offers a safety guideline. It could optionally mention response behavior, but the output schema likely covers that, so no significant gap exists.

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%, so the baseline is 3. The description references 'object ID and block ID' which maps to the 'id' and 'blockId' parameters, but adds no additional meaning beyond the schema's descriptions. The apiToken parameter is not mentioned, but the schema already covers it thoroughly.

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 'Delete one existing Capacities block by object ID and block ID', using a specific verb and resource. It distinguishes from sibling tool 'delete_object' by targeting blocks, and the title reinforces this. This is a clear, non-tautological purpose statement.

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 explicit guidance: 'read structured content first and use only when the deletion is intentional.' It also highlights a key consequence ('Nested child blocks are deleted with their parent'), which helps the agent decide when to use the tool. However, it does not explicitly name alternative tools or state when NOT to use it, so it falls short of a 5.

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