Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

restore_policy_version

Restore a policy draft to a prior version using its version ID, preserving the current draft as a snapshot for undo capability.

Instructions

Roll a policy's DRAFT back to an earlier version. Takes the versionId (a UUID from list_policy_versions), NOT the checkpoint number. The current draft is snapshotted first, so this is itself undoable. It changes only the draft — what is live stays live until a human approves a new publish.

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>",
      "expectedVersion": "<expectedVersion>"
    },
    "name": "restore_policy_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe policy's id.
versionIdYesThe version row's UUID.
expectedVersionYesThe draft version you last read — 409 if stale.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses key behaviors: snapshots the current draft (making it undoable), only affects draft (live stays live), and requires a UUID versionId. With no annotations, the description fully bears the transparency burden and does so excellently.

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?

Three sentences: first states main purpose, second clarifies critical parameter nuance, third explains behavior and scope. No redundant words, front-loaded with the action verb.

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 3 required params, the description covers what the tool does, how it works, and key behavioral details. Lacks explicit mention of return format but is acceptable for a state-changing tool with clear side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, each param has description. The description adds significant value by clarifying that versionId is a UUID from list_policy_versions (not a checkpoint number) and explaining the undo mechanism. This goes beyond the schema's basic type info.

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 uses a specific verb ('Roll a policy's DRAFT back to an earlier version') and clearly identifies the resource and action. It distinguishes from sibling restore tools by specifying it targets only the draft, not live or deleted policies.

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?

Explicitly states that versionId must come from list_policy_versions and not a checkpoint number. Clarifies that the operation is undoable (snapshots current draft) and only affects draft, not live policy. Lacks explicit 'when not to use' but context is sufficient.

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