Skip to main content
Glama
AxonityAI

Axonity Flow MCP Server

Official
by AxonityAI

list_deleted_skill_versions

List a skill's deleted versions to identify restore candidates. Deleted version numbers remain reserved, so gaps in numbering are expected.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe skill's id.
Behavior4/5

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

No annotations provided, so description carries burden. It explains that deleted version numbers remain reserved and gaps are expected, addressing a common concern. Shows it is a read-only listing.

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. First sentence states purpose and relationship to restore tool. Second adds important behavioral note. No unnecessary 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?

Simple tool with single parameter and no output schema. Description covers purpose and a key behavioral trait. Could optionally mention output fields but not required for a list tool.

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?

Only one parameter 'id' with schema description 'The skill's id.' Description does not add extra meaning beyond schema. 100% schema coverage means baseline 3 is appropriate.

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?

Clearly states it lists deleted version rows of a skill, specifically as restore candidates. Distinguishes from siblings like list_skill_versions by specifying 'deleted'.

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 it lists restore candidates, indicating usage before restore_deleted_skill_version. Does not explicitly mention when not to use, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AxonityAI/axonity-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server