Skip to main content
Glama

create_workflow

Create a workflow (confirm-gated; Coach Pro or gym plan required). Either pass templateKey (from list_workflow_templates) to switch on a ready-made one, or give name, triggerType, optional days, and actionType + text. actionType 'send_message' sends text as written ({{clientName}} etc. allowed); 'ai_message' treats text as an instruction and has AI draft a message in the coach's voice, held for approval unless requireApproval is false; 'notify_coach' only reminds the coach. Safety limits are built in: 8am–9pm client-local time, max 2 workflow messages per client per day, each event fires once.

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": "create_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNochat
daysNo
nameNo
textNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
actionTypeNo
templateKeyNo
triggerTypeNo
requireApprovalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the confirm gate (preview-only unless confirm is true), the approval hold for 'ai_message' unless requireApproval is false, and concrete safety limits (8am–9pm client-local, max 2 messages per client per day, single fire per event). These are exactly the operational constraints an agent needs before calling and are not present in readOnlyHint/destructiveHint/openWorldHint.

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?

Front-loads the core action and constraints in the first sentence, then layers the two paths and action semantics. It is dense and semicolon-heavy but nearly every clause adds usable information; a small amount of formatting could improve scanability.

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 9-parameter mutation tool with no output schema and sparse schema descriptions, the description covers plan requirements, the confirm gate, approval behavior, and runtime safety limits. Remaining gaps are the undocumented `via` parameter, triggerType value space, and what the preview response contains.

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?

Schema description coverage is only 11%, so the description carries the burden, and it does much of it: it explains templateKey's source, the manual field set, and the three actionType behaviors with how `text` is interpreted in each case. The `via` parameter (chat/push/email) and valid triggerType values are never explained anywhere, leaving real gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource plus two gating conditions (confirm-gated, plan requirement) and immediately names the two creation paths (templateKey vs. manual fields). It does not address the closely named sibling create_gym_workflow, so an agent must still infer which creator applies to a gym plan, keeping this at 4 rather than 5.

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 clear routing guidance: pass `templateKey` from list_workflow_templates for a ready-made workflow, otherwise supply name/triggerType/days/actionType+text. It also implicitly notes that execution requires confirm=true or you get a preview. No explicit when-not-to-use-this-instead-of-update_workflow guidance, hence 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.