Skip to main content
Glama

delete_flow_entity

DestructiveIdempotent

Permanently delete a condition set, variable, quota, permutation set, or quota status link, with confirm: true. Consequences vary by entity_kind: condition sets may break flow branching and quota references; quotas lose their counter history; quota_status_link immediately revokes the vendor's access. There is no recovery.

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>",
      "entity_kind": "<entity_kind>",
      "entity_id": "<entity_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_flow_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Consequences vary by entity_kind: deleting a condition_set may break flow branching and quota references; deleting a quota permanently erases its counter history; deleting a quota_status_link immediately revokes the vendor's access. There is no recovery.
entity_idYesEntity UUID
survey_idYesSurvey UUID
entity_kindYesKind of flow entity to delete

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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, but the description goes further by disclosing what actually breaks per entity_kind (flow branching, quota references, counter history, vendor access) and that 'There is no recovery.' That consequence detail is genuinely beyond the structured hints, though it does not cover permission requirements or cascade behavior for dependent entities.

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?

Three sentences, front-loaded with the action and its entity scope, followed by consequences and the irreversibility warning. No filler, no restatement of the tool name, and the most alarming fact ('There is no recovery') lands last for emphasis.

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?

An output schema exists, so return values need no explanation, and the description covers entity scope, the confirm gate, per-kind consequences, and irreversibility. The remaining gap is that nothing is said about required permissions or whether deleting a condition_set or quota detaches or orphans dependent objects.

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 entity_kind enum are already documented. The description's per-kind consequence notes mirror the text already present in the confirm parameter's schema description, so it adds little meaning beyond what the schema supplies. Baseline 3 applies.

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 ('Permanently delete') plus an explicit enumeration of the resources it operates on: condition set, variable, quota, permutation set, quota status link. This lets an agent distinguish it from sibling deleters like delete_block or delete_question without opening any schema.

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 gives one hard prerequisite ('with confirm: true'), which is real usage guidance, but it never says when to prefer this over edit_flow or read_flow, nor does it state any exclusion or pre-check step before deleting. Usage is implied by the entity enumeration rather than stated.

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