Skip to main content
Glama

delete_quality_rule

DestructiveIdempotent

Permanently delete a response-quality rule with confirm: true — cannot be undone, and previously computed flags are not retroactively cleared.

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": {
      "survey_id": "<survey_id>",
      "rule_id": "<rule_id>",
      "rule_kind": "<rule_kind>",
      "confirm": "<confirm>"
    },
    "name": "delete_quality_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Deleting a quality rule is permanent and stops flagging past and future responses against it — previously computed flags are not retroactively cleared.
rule_idYesRule UUID
rule_kindYesQuality rule type
survey_idYesSurvey UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's main value-add is the consequence detail: the action is irreversible and existing computed flags are not retroactively cleared. That side-effect disclosure is genuinely beyond what the annotations convey, though it does not address permission requirements or effect on in-flight collection.

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?

A single front-loaded sentence that leads with the permanence warning and the required flag, with zero redundant wording. Every clause (permanent, confirm, flags not cleared) carries distinct information.

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?

With an output schema present and annotations covering the safety profile, the description only needs to add consequence context, which it does. The remaining gap is minor: nothing about authorization level or whether the rule must be inactive before deletion.

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%, so all four parameters including the rule_kind enum and the confirm requirement are already documented. The description's mention of 'confirm: true' merely restates the schema and adds no syntax, format, or edge-case meaning.

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

Purpose4/5

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

The description pairs a specific verb ('Permanently delete') with a specific resource ('a response-quality rule'), making the operation unambiguous. It does not explicitly contrast itself with the adjacent edit_quality_rule or read_quality_rule siblings, but the delete verb carries that distinction implicitly.

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

Usage Guidelines3/5

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

It states a hard precondition ('with confirm: true') that an agent must satisfy, which is useful guidance. However, it gives no when-to-use vs. when-not guidance and no pointer to edit_quality_rule as the non-destructive alternative for modifying a rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources