Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_output_schema_version

Permanently delete a version of an output schema (except draft and published). Confirm the action to proceed; the version can be restored until purged.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesThe output_schema'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?

With no annotations, the description carries full burden. It discloses permanent removal, protection of certain versions, recovery possibility, and eventual purge. It avoids contradictions but could be more explicit about the confirm parameter's role and any prerequisites.

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 brief (two sentences) and front-loaded with the core action. No unnecessary words or redundancy.

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?

The description adequately explains the tool's purpose, constraints, and recovery path. It does not cover error scenarios (e.g., invalid version), but given the simple operation, 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 description coverage is 100%, so the schema already documents all parameters. The description does not add extra parameter-level details, so it meets the baseline of 3.

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 a version entry from an output_schema's history. It distinguishes the tool by noting that working draft and published versions are protected, differentiating it from delete_output_schema and other version management tools.

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 provides context on when to use this tool (to delete specific version entries) and mentions the recovery alternative (restore_deleted_output_schema_version). However, it does not explicitly state when not to use it, such as for deleting the entire schema or for deleting draft/published versions.

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