Control Plane

Delete a Resource

delete_resource

Destructive

Delete one Control Plane resource by kind + name — the single delete tool for every deletable kind. Deleting a secret breaks the workloads that read it (cpln://secret/NAME) and any GVC pull secret or domain TLS that uses it. Deletes on the call. Before calling, read the resource and tell the user what the deletion removes and which dependents break, and proceed only on their explicit approval. Deletion is permanent.

Input Schema

TableJSON Schema

Name	Required	Description
`gvc`	No	GVC slug — REQUIRED only for GVC-scoped kinds (workload, identity, volumeset); ignored otherwise.
`org`	No	Organization slug.
`kind`	Yes	Resource kind to delete.
`name`	Yes	Name of the resource to delete. Read the resource and present what the deletion removes and breaks, then call only on the user's explicit approval. Never invent a name. Most kinds use lowercase kebab-case names; exceptions: domain = the full hostname ("app.example.com"), image = NAME or NAME:TAG ("my-app:v1.2").

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`data`	No	The full result. Read this, not only the summary.
`details`	No
`summary`	Yes
`nextSteps`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / kind / enum

Previous value: -[
-  "workload",
-  "identity",
-  "volumeset",
-  "gvc",
-  "policy",
-  "group",
-  "domain",
-  "cloudaccount",
-  "agent",
-  "ipset",
-  "mk8s",
-  "serviceaccount",
-  "image",
-  "user"
-]New value: +[
+  "workload",
+  "identity",
+  "volumeset",
+  "gvc",
+  "secret",
+  "policy",
+  "group",
+  "domain",
+  "cloudaccount",
+  "agent",
+  "ipset",
+  "mk8s",
+  "serviceaccount",
+  "image",
+  "user"
+]

Changed20 schema fields changedSep 30, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / gvc / maxLength
```
Removed value: -63
```
removedInput schema / properties / gvc / minLength
```
Removed value: -1
```

removedInput schema / properties / gvc / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

changedInput schema / properties / kind / description

Previous value: -"Resource kind to delete. One of: workload, identity, volumeset, gvc, policy, group, domain, cloudaccount, agent, ipset, mk8s, serviceaccount, image, user."New value: +"Resource kind to delete."

removedInput schema / properties / name / maxLength
```
Removed value: -257
```
removedInput schema / properties / name / minLength
```
Removed value: -1
```

changedInput schema / properties / org / description

Previous value: -"Organization slug (lowercase kebab-case). NEVER guess — if the user has not named one, ask. On org-not-found, stop and ask; do not retry variants."New value: +"Organization slug."

removedInput schema / properties / org / maxLength
```
Removed value: -63
```
removedInput schema / properties / org / minLength
```
Removed value: -1
```

removedInput schema / properties / org / pattern

Removed value: -"^[a-z0-9]([a-z0-9-]{0,61}[a-z0-9])?$"

changedInput schema / required

Previous value: -[
-  "kind",
-  "org",
-  "name"
-]New value: +[
+  "kind",
+  "name"
+]

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / data / description

Previous value: -"The full machine-readable result — list rows, the resource object, query results. Read THIS, not just the summary."New value: +"The full result. Read this, not only the summary."

addedOutput schema / properties / details
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / nextSteps / description

Removed value: -"Recommended follow-up actions for this task, in order."

removedOutput schema / properties / ok / description
```
Removed value: -"Whether the call succeeded."
```
removedOutput schema / properties / summary / description
```
Removed value: -"One-line summary of the result."
```

Changed2 schema fields changedAug 14, 2026

changedInput schema / properties / kind / description

Previous value: -"Resource kind to delete. One of: workload, identity, volumeset, gvc, secret, policy, group, domain, cloudaccount, agent, ipset, mk8s, serviceaccount, image, user."New value: +"Resource kind to delete. One of: workload, identity, volumeset, gvc, policy, group, domain, cloudaccount, agent, ipset, mk8s, serviceaccount, image, user."

changedInput schema / properties / kind / enum

Previous value: -[
-  "workload",
-  "identity",
-  "volumeset",
-  "gvc",
-  "secret",
-  "policy",
-  "group",
-  "domain",
-  "cloudaccount",
-  "agent",
-  "ipset",
-  "mk8s",
-  "serviceaccount",
-  "image",
-  "user"
-]New value: +[
+  "workload",
+  "identity",
+  "volumeset",
+  "gvc",
+  "policy",
+  "group",
+  "domain",
+  "cloudaccount",
+  "agent",
+  "ipset",
+  "mk8s",
+  "serviceaccount",
+  "image",
+  "user"
+]

First observedJun 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's job is to add consequence detail beyond the flag — and it does: 'deleting a secret breaks the workloads that read it ... and any GVC pull secret or domain TLS that uses it,' plus 'Deletes on the call' (immediate write, no dry-run) and 'Deletion is permanent' (irreversibility). It does not cover permissions needed or whether deletion is rate-limited/eventually-consistent, so it stops short of a 5.

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?

Four sentences, each earning its place: identity, blast radius, timing, and required pre-call procedure, with the most consequential facts (blast radius, irreversibility) front-loaded after the one-line purpose. No restated schema content or filler.

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, open-world mutation with four parameters, an output schema that documents return values, and rich schema descriptions, the description supplies exactly what the structured fields cannot: dependent-risk examples, immediacy of the write, and the approval workflow an agent must follow. Nothing an agent needs to call this safely 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 description coverage is 100% — the schema already documents gvc scoping, org, the 15-value kind enum, and the per-kind name-format exceptions (domain = full hostname, image = NAME:TAG). The description adds the 'kind + name' identity framing but no syntax beyond the schema, so the baseline 3 is correct.

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?

States a specific verb (delete) and resource (Control Plane resource identified by kind + name) and explicitly claims scope as 'the single delete tool for every deletable kind.' This distinguishes it from the many create_/update_/remove_ siblings without the agent needing to open another schema.

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

Usage Guidelines5/5

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

Gives an explicit pre-call workflow: read the resource, tell the user what will be removed and which dependents break, and proceed only on explicit approval. The 'for every deletable kind' phrasing also routes the agent here rather than to a kind-specific alternative, which is the only alternative available.

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

All Control Plane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.