Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_persona_version

Permanently delete a specific version from a persona's history, excluding the working draft and published version. Can be recovered until purged.

Instructions

Permanently remove one entry from a persona's version history. The working draft and the currently published version are protected and cannot be targeted this way. Recoverable with restore_deleted_persona_version until it is purged for good.

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>",
      "versionId": "<versionId>",
      "confirm": "<confirm>"
    },
    "name": "delete_persona_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe persona's id.
confirmYesMust be true. Acknowledges you understand this is destructive.
versionIdYesThe version row's UUID (not the checkpoint number).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Despite no annotations, the description discloses destructive nature ('permanently remove'), recovery window ('until purged'), and protected versions. It effectively communicates key behavioral traits beyond what the schema provides.

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 containing all essential information with no redundancy. Front-loaded with the core action, then constraints and recovery details. Every sentence earns its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a delete tool with no output schema, the description adequately covers effects, constraints, recovery path, and finality. It provides sufficient context for correct invocation and understanding of consequences.

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 covers 100% of parameters with descriptions. The description does not add additional meaning to parameters beyond what is already in the schema. Baseline score 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 clearly states the action 'Permanently remove one entry' from a persona's version history, using a specific verb and resource. It distinguishes from sibling tools like restore_deleted_persona_version.

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

Usage Guidelines5/5

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

Provides explicit guidance on when not to use (protected draft and published versions) and mentions an alternative (restore_deleted_persona_version) for recovery. This helps the agent choose correctly.

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