Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_conditional_trigger

Permanently remove a conditional trigger with irreversible deletion. Confirmation is required to prevent accidental data loss.

Instructions

Delete a conditional trigger. HARD delete — the row is removed and cannot be restored.

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": {
      "triggerId": "<triggerId>",
      "confirm": "<confirm>"
    },
    "name": "delete_conditional_trigger"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Destructive and irreversible — ask your human first.
triggerIdYesThe conditional trigger's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

The description explicitly states 'HARD delete — the row is removed and cannot be restored', which reveals the destructive and irreversible nature. This is valuable behavioral context beyond the basic purpose, especially since no annotations are provided.

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?

Two sentences that are front-loaded: the first states the purpose, the second adds critical behavioral context. No unnecessary words or fluff.

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?

For a delete operation with two parameters and no output schema, the description is quite complete. It covers the action, irreversibility, and implication of confirmation. Could optionally mention permissions or return value, but not strictly necessary.

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?

The input schema already has 100% description coverage for both parameters (confirm and triggerId). The tool description adds no additional parameter-specific information beyond what is in the schema, so a baseline of 3 is appropriate.

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?

The description 'Delete a conditional trigger' clearly states the verb (delete) and the resource (conditional trigger). It distinguishes from sibling delete operations for other entities like webhook triggers and cron schedules.

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?

While the description implies use when needing to delete a conditional trigger, it does not explicitly state when not to use or provide alternatives (e.g., updating vs deleting). Lack of explicit usage guidance beyond the action itself.

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