Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_policy_version

Permanently remove a policy version from its history, except for the working draft and currently published version. Deleted versions can be restored until purged.

Instructions

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

Input Schema

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

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

No annotations provided, so description carries full weight. It discloses destructive behavior ('permanently remove'), protection of certain versions, and recoverability until purge. Missing details on authorization or side effects, but sufficient for a mutation 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?

Two concise sentences with no fluff. First sentence states the action and constraints; second sentence adds recovery context. Front-loaded with essential information.

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 and no annotations, the description covers purpose, constraints, and behavioral impact. It mentions an alternative tool. Missing return value info, but adequate for agent decision-making.

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 baseline is 3. Description does not add additional meaning beyond schema; e.g., it doesn't elaborate on the confirm parameter's purpose beyond acknowledging destruction. No extra context provided.

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 states 'Permanently remove one entry from a policy's version history', using a specific verb and resource. It distinguishes from siblings by noting protected versions and mentioning recoverability via restore_deleted_policy_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?

Explicitly states which versions cannot be targeted (working draft, currently published) and provides an alternative tool for recovery (restore_deleted_policy_version). This gives clear when-to-use and when-not-to-use guidance.

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