Skip to main content
Glama
Sign In
AIMFP

AIMFP

by aryanduntley
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_flow

Destructive

Delete a flow after file validation, with a mandatory deletion note specifying the reason, severity, and source.

Instructions

Delete flow with file validation

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": {
      "flow_id": "<flow_id>",
      "note_reason": "<note_reason>",
      "note_severity": "<note_severity>",
      "note_source": "<note_source>",
      "note_type": "<note_type>"
    },
    "name": "delete_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesFlow ID to delete
note_reasonYesDeletion reason
note_severityYes'info', 'warning', 'error'
note_sourceYes'ai' or 'user'
note_typeYes'entry_deletion'entry_deletion

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.37.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true. The description adds 'file validation' hinting at additional side effects, but does not elaborate on what validation occurs or its implications.

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

Conciseness4/5

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

Extremely concise at 5 words, no fluff. However, could benefit from more detail without becoming verbose.

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?

For a destructive mutation with 5 required parameters and no output schema, the description lacks details on post-deletion effects, file validation specifics, and typical use case context.

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?

All 5 parameters are described in the input schema with clear descriptions. The description adds no further meaning beyond what the schema already provides.

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 flow with file validation' clearly states the action (delete) and resource (flow) with a specific qualifier (file validation), distinguishing it from other delete tools in the sibling list.

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

Usage Guidelines2/5

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

No guidance on when to use delete_flow versus alternatives like delete_file or update_flow. No prerequisites or conditions are mentioned.

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