Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_skill_version

Permanently delete a specific version of a skill, excluding the working draft and published version. The version can be restored before it is purged.

Instructions

Permanently remove one entry from a skill's version history. The working draft and the currently published version are protected and cannot be targeted this way. Recoverable with restore_deleted_skill_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_skill_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe skill'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.2/5.0
Behavior4/5

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

Without annotations, the description bears full burden. It discloses permanence, protection constraints, and recovery path. It does not detail side effects or permissions, but overall provides sufficient transparency for a deletion tool.

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?

The description is two sentences, front-loaded with the action and constraints, and the second adds recovery info. No wasted words.

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?

Given no output schema, the description covers the action, constraints, and recovery. It does not explain return values or error cases, but for a delete tool with sibling context, it is sufficiently complete.

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 coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions, which are already clear.

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 verb 'remove' and the resource 'entry from a skill's version history', and distinguishes from related tools like delete_skill or restore_skill_version by mentioning protected versions and recovery via restore_deleted_skill_version.

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

Usage Guidelines4/5

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

The description specifies that the working draft and currently published version are protected and cannot be targeted, and that the deletion is recoverable until purged. This provides clear context, though it does not explicitly name alternative tools.

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