Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api settings global destroy

ciso_assistant_api_settings_global_destroy
DestructiveIdempotent

Permanently deletes a global API setting by ID in CISO Assistant and requires explicit confirmation for the destructive action.

Instructions

api_settings_global_destroy

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": "ciso_assistant_api_settings_global_destroy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.12
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
      +  "type": "boolean"
      +}
  2. First observedv2.3.6

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that – not what record gets removed, whether the deletion cascades, whether elevated permissions are required, or whether it is reversible. No contradiction with annotations, but zero added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short only because it contains no information; it is under-specification rather than conciseness. A bare snake_case identifier is not a front-loaded summary of anything an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation on global application settings with no output schema and one undocumented parameter, which is exactly the case where the description must carry the load. It says nothing about what is destroyed or how to obtain the required 'id', so an agent cannot call it safely from the definition alone.

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 50%: the 'confirm' parameter is documented in the schema itself, while 'id' has no description anywhere. Per the rubric, a description adds little here, but it also fails to clarify what 'id' identifies (a settings entry key? a record UUID?) for a global-settings object, leaving a real ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is just the tool name re-serialized as 'api_settings_global_destroy'; it restates the name rather than describing the action. An agent can infer deletion of a global setting only from the 'destroy' suffix in the name, not from any explanatory text, and nothing distinguishes it from the ~200 other *_destroy siblings.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no preconditions, no mention of alternatives such as ciso_assistant_api_settings_global_partial_update or _update, and no statement of what a global setting actually is. The agent is left to guess entirely.

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