Skip to main content
Glama

delete_csp

Destructive

Permanently remove a contextual security policy by its UUID, immediately lifting its restrictions. Use the reversible toggle option instead if the policy may be needed again.

Instructions

Permanently remove a contextual security policy and immediately remove its restrictions. Use toggle_csp to suspend it reversibly.

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": {
      "csp_id": "<csp_id>"
    },
    "name": "delete_csp"
  }
}

Input Schema

NameRequiredDescriptionDefault
csp_idYesUUID of the CSP policy to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / csp_id / description
      Previous value: -"UUID da CSP a remover"New value: +"UUID of the CSP policy to remove"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is carried structurally. The description does add real value by saying the removal is permanent and that restrictions stop applying immediately, but it says nothing about the non-idempotent behavior (what happens on a second delete) or any confirmation/auth requirements. Useful but modest beyond what annotations already provide.

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?

Two tight sentences with the permanence warning front-loaded and the alternative following. No wasted wording; slightly more compact framing could merge the permanence and restriction-removal clauses, but this is close to optimal for the content given.

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, non-idempotent destructive delete with no output schema and full annotation coverage, the definition supplies everything an agent needs: what is removed, that it is irreversible, and the safe alternative. Nothing material 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 csp_id parameter is fully documented as a UUID in the schema. The description adds no format, sourcing, or lookup guidance beyond that, so the baseline 3 applies — the schema does all the work here.

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 and resource ("Permanently remove a contextual security policy") and immediately scopes the effect ("immediately remove its restrictions"). It also distinguishes itself from the reversible sibling by contrasting with toggle_csp, so an agent can tell the two apart without opening a 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?

Explicitly names the alternative (toggle_csp) and the condition that selects it — suspend reversibly. That is a direct when-to-use-this-versus-that instruction, leaving nothing to inference for the main decision an agent faces here.

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

Deploy Server

Other Tools