Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_deleted_prompt_snippet_versions

List deleted versions of a prompt snippet to find restore candidates, with reserved version numbers and expected gaps.

Instructions

List a prompt_snippet's deleted version rows — restore candidates for restore_deleted_prompt_snippet_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_prompt_snippet_versions"
  }
}

Input Schema

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

With no annotations, description discloses that deleted version numbers remain reserved and gaps are normal, adding important behavioral insight beyond a simple list operation.

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 crisp sentences: first states purpose, second clarifies a behavioral nuance. 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?

For a simple list tool with one parameter, the description covers purpose and a key behavioral detail. Could mention pagination or returned fields, but not essential.

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 has 100% coverage with parameter description 'The prompt_snippet's id.' Description does not add extra meaning beyond that.

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?

Explicitly states 'List a prompt_snippet's deleted version rows' with clear verb and resource. Distinguishes from sibling tools like list_prompt_snippet_versions by specifying 'deleted', and ties to restore use case.

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?

Provides context that these are restore candidates and explains version numbering behavior. Could explicitly state when to use this over list_prompt_snippet_versions, but purpose is clear.

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