Skip to main content
Glama
Sign In
Axonity Flow MCP Server

Axonity Flow MCP Server

Official
by AxonityAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_cron_schedule

Schedule a workflow to run automatically using a cron expression. Define the trigger, timezone, and enable or disable the schedule.

Instructions

Schedule a workflow to run on a cron expression.

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": {
      "workflowId": "<workflowId>",
      "triggerId": "<triggerId>",
      "cronExpr": "<cronExpr>"
    },
    "name": "create_cron_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoDefaults to true.
cronExprYesThe cron expression, e.g. "0 9 * * 1-5" for weekdays at 09:00.
timezoneNoIANA timezone, e.g. "Europe/Brussels". Defaults to UTC.
triggerIdYesThe id of the trigger node in the workflow document.
workflowIdYesThe workflow's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether it creates a new schedule, required permissions, side effects, or idempotency. It only restates the action.

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 a single sentence that is concise and front-loaded, containing no unnecessary words or information.

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

Completeness2/5

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

The description is too brief for a mutation tool with 5 parameters and no output schema. It does not explain what the tool returns, prerequisites (e.g., workflow must exist), or behavior on duplicate schedules.

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 description coverage is 100%, so the description adds no additional meaning beyond what is in the schema. The baseline of 3 is appropriate as the schema already documents all parameter semantics.

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 'Schedule a workflow to run on a cron expression' clearly specifies the action (schedule), resource (workflow), and mechanism (cron expression). It effectively distinguishes from siblings like list_cron_schedules and delete_cron_schedule.

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 implies usage for periodic scheduled runs via cron, which distinguishes from event-driven triggers like create_webhook_trigger. However, it lacks explicit when-to-use or when-not-to-use guidance.

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