Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_deleted_policy_versions

List a policy's deleted version rows to find restore candidates. Deleted version numbers remain reserved, so gaps are expected.

Instructions

List a policy's deleted version rows — restore candidates for restore_deleted_policy_version. Deleted version numbers stay reserved (not reused), so gaps in the numbering are expected, not corruption.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe policy's id.

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?

No annotations are provided, so the description must carry the full burden. It discloses that deleted version numbers are reserved and gaps are normal, which is a behavioral trait beyond a simple listing. It does not cover permissions, rate limits, or response format, but for a read-only list tool, the core behavior is adequately described.

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, no unnecessary words. The first sentence states the purpose and links to the restore counterpart. The second adds an important behavioral nuance. Information is front-loaded and every sentence earns its place.

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 the tool has one required parameter, no output schema, and no annotations, the description sufficiently covers its purpose and a key behavioral insight. It could briefly mention the output structure (e.g., list of rows) but the lack of detail is acceptable for a simple list operation.

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%, with the single parameter 'id' already described in the schema as 'The policy's id.' The description adds no further parameter details, so it meets the baseline of 3 as per the rule for high schema coverage.

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 specifies the exact action: listing deleted version rows for a policy, and explicitly connects these to restore candidates for restore_deleted_policy_version. It distinguishes from sibling tools like list_policy_versions by focusing on deleted versions, and adds a key behavioral detail about reserved version numbers.

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 states that these are restore candidates and explains that gaps in version numbers are expected, which helps the agent interpret results correctly. It implicitly contrasts with list_policy_versions but does not explicitly exclude other usage scenarios or state when not to use this tool.

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