Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_flow_step_prompts

List the system and user prompt snippets for a flow step, showing each entry's link id and display order to review the current prompt composition before modification.

Instructions

List the prompt snippets attached to a flow step — its system and user prompt stacks, each entry with its link id and display order. This is how you see a step's current prompt composition before changing it. Excludes wildcard snippets (see list_wildcard_prompts). Read-only.

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": {
      "flowStepId": "<flowStepId>"
    },
    "name": "list_flow_step_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowStepIdYesThe flow step's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.5/5.0
Behavior4/5

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

Since no annotations are provided, the description carries full burden. It declares the tool as read-only, which is a key behavioral trait. It describes the return structure (system and user prompt stacks with link id and display order). While it doesn't mention rate limits or pagination, the description is sufficient for a simple read-only list tool.

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 three sentences, front-loaded with the main purpose. Every sentence adds value, including the exclusion of wildcard snippets and the read-only nature. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter and no output schema, the description is complete. It explains what the tool returns, its read-only behavior, and how it differs from related tools. No gaps remain given the tool's simplicity.

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% for the single required parameter flowStepId, which already has a clear description. The tool description does not add additional meaning or format details beyond what the schema provides, so 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?

Description clearly states the tool lists prompt snippets attached to a flow step, specifying system and user prompt stacks with link id and display order. It distinguishes itself from the sibling tool list_wildcard_prompts by explicitly excluding wildcard snippets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'This is how you see a step's current prompt composition before changing it,' indicating when to use it (before modification). It also directs users to list_wildcard_prompts for excluded snippets, providing clear guidance on alternatives.

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