Simpler.Asia

workflow_create

Create a workflow — an AI operator's job: validates definition_json (a { nodes, edges, schedule? } graph) against the platform's node vocabulary, refusing unknown node types and any comms/message-shaped step that isn't a prepare_output node, since the platform prepares outputs but never sends them. trigger_type 'schedule' requires a schedule block; next_run_at is then computed server-side from it, never from a caller value. is_active defaults to 0 (draft) — going live is a separate explicit choice. NEXT: workflow_update to fix a rejected definition or flip is_active.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "workflow_create"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`is_active`	No
`role_name`	No
`description`	No
`next_run_at`	No
`trigger_type`	No
`imported_from`	No
`definition_json`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the generic annotations: discloses that definition_json is validated against a node vocabulary, that unknown node types and non-prepare_output comms steps are refused, that next_run_at is computed server-side and ignores any caller value, and that is_active defaults to 0. These are exactly the non-obvious behaviors an agent must know before calling.

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?

Front-loads the action and then layers validation rules, defaults, and the next step in a compact sequence. Every sentence conveys a distinct constraint; nothing is repeated from the schema or annotations.

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?

Covers domain rules, defaults, side effects, and the follow-up tool, which is most of what an agent needs for an 8-parameter creation call with no output schema. It does not indicate what is returned (e.g., an id) or note that no parameters are required, leaving a small gap.

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

Parameters4/5

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

With 0% schema description coverage the description carries the burden, and it covers the highest-risk parameters: definition_json's { nodes, edges, schedule? } shape, the trigger_type 'schedule' requirement, next_run_at being ignored, and is_active's default. It leaves name, role_name, description, imported_from, and the manual/webhook trigger modes unaddressed, so compensation is strong but incomplete.

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?

States a specific verb and resource ('Create a workflow') and immediately defines what is being created ('an AI operator's job') plus its validation responsibility. It is unmistakable against siblings like workflow_update, workflow_read, and workflow_list.

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?

Gives explicit routing: 'NEXT: workflow_update to fix a rejected definition or flip is_active', and clarifies that going live is a separate choice rather than part of creation. It stops short of naming when not to create (duplicate names, existing workflows), but the create-vs-update split is clear.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?