Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api metrology dashboards destroy

ciso_assistant_api_metrology_dashboards_destroy
DestructiveIdempotent

Deletes a metrology dashboard by its ID, with an optional confirmation flag for destructive operations when the client cannot answer a prompt.

Instructions

api_metrology_dashboards_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_metrology_dashboards_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

D1.7/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 readOnlyHint=false, so the safety profile is known. The description adds nothing beyond that — no statement of what is destroyed (widgets, metric samples?), whether deletion cascades, or whether it is reversible. No contradiction with annotations, but no value added either.

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 trivially short, but this reflects under-specification rather than conciseness — there is no informative content to front-load. The single tokenized phrase does not even read as a sentence.

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

Completeness1/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 no output schema and partial parameter documentation, the description supplies none of the needed context: target object identity, cascade effects, permission requirements, or the purpose of the confirm flag. An agent cannot safely invoke this tool from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the undocumented 'id' parameter gets no explanation in the description; its format (UUID vs slug) and lookup semantics are unknown. The 'confirm' flag's confirmation behavior is explained only by the schema, not the description. The description fails to compensate for the coverage gap.

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 literally the tool name ("api_metrology_dashboards_destroy") with no verb or resource explanation added. Only the implicit 'destroy' token hints at deletion; nothing states what a metrology dashboard is or what deleting one entails. Tautological restatement of name/title.

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?

No when-to-use, when-not-to-use, or prerequisite guidance appears anywhere in the description. It does not mention the sibling create/update/retrieve tools or explain when a dashboard should be removed rather than modified. The agent must infer everything from the name alone.

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