Skip to main content
Glama
AxonityAI

Axonity Flow MCP Server

Official
by AxonityAI

validate_workflow

Validate a workflow's readiness by checking for structural and catalog issues. Use workflowId for catalog-aware validation or document for stateless structural checks. Returns launchable status and issues list.

Instructions

Check a workflow for problems. Returns launchable, catalogChecked, and an issues list (each with code, message, severity, stepIds, edgeIds).

Pass EXACTLY ONE of workflowId or document — they answer different questions:

  • workflowId → validates the STORED workflow against this tenant's catalog. This is the real 'can this run?': it confirms the agents, tools and flows the steps reference actually exist. Answers catalogChecked: true.

  • document → validates the document you pass, STATELESSLY. No database, so read-only service tokens can call it, but with no catalog the cross-entity checks cannot run: launchable here means 'structurally sound', NOT 'this will run'. Answers catalogChecked: false. Use it for a draft you have not saved, or for fast feedback while editing.

A green verdict is what a reader remembers, so check catalogChecked before telling anyone a workflow is ready. Call this after apply_workflow_mutations and before request_publish_workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
documentNoValidate this document statelessly (as returned by read_workflow). Omit if you are passing a workflowId.
workflowIdNoValidate this STORED workflow against the tenant catalog. Omit if you are passing a document.
Behavior5/5

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

No annotations provided, so description fully covers behavior. Discloses that workflowId validates against tenant catalog, document is stateless and can be called with read-only tokens, but catalog checks won't run. Clarifies what launchable means in each case and warns to check catalogChecked before declaring readiness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear separation of modes, but slightly verbose. However, the extra detail is justified given the complexity. Front-loads return fields, making key info immediately visible.

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?

Covers all necessary aspects: return fields, two operational modes, valid use cases, limitations, and positioning in workflow editing lifecycle. No gaps given the tool's complexity and lack of output schema.

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

Parameters5/5

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

Schema coverage is 100%, but description adds significant value: forces mutual exclusivity, explains the different behaviors and use cases for each parameter, and clarifies the meaning of 'launchable' based on parameter chosen.

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 checks a workflow for problems and returns specific fields (launchable, catalogChecked, issues). Distinguishes between two modes: workflowId validates stored workflow against catalog, document statelessly validates a draft. No ambiguity.

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 instructs to pass exactly one of workflowId or document. Explains when to use each: workflowId for real 'can this run?' after saving, document for drafts or fast feedback. Also specifies to call after apply_workflow_mutations and before request_publish_workflow, providing a clear sequence.

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