Skip to main content
Glama

process-create_definition

process-create_definition

Define and save reusable process definitions for automated workflows, specifying action type (webhook, automation, AI agent) and execution parameters.

Instructions

Creates a reusable process definition for automated workflows. Use with process tasks (task_type='process').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_typeYesType of action: http_webhook, internal_automation, or ai_agent
agent_configNoFor ai_agent: {prompt_template, input_items, output_item_type}
automation_configNoFor internal_automation: {operations: [{type, ...}]}
case_idYesCase ID (@rid format)
completion_stepsNoSteps the executing LLM must complete before calling complete_task. Define per-process (e.g., software changes: 'compile, commit, deploy, verify'; research: 'summarize findings in a note'). If blank, generic instructions are used.
descriptionNoWhat this process does
execution_modeNosync (wait for result) or async (background job). Default: async
nameYesDefinition name
retry_countNoNumber of retries on failure
timeout_secondsNoOverall execution timeout
triggers_sentryNoSentry ID to trigger on successful completion
versionNoVersion string (default: 1.0)
webhook_configNoFor http_webhook: {url, method, headers, body_template, timeout_ms}
Behavior2/5

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

No annotations provided, and description only states creation without disclosing side effects, required permissions, or return behavior. Minimal behavioral insight.

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?

Two concise sentences with front-loaded action and usage context. No extraneous 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?

Complex tool with 13 parameters, nested objects, no output schema. Description leaves out details on action_type implications, required fields usage, and result expectations.

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%, so baseline is 3. Description adds no additional parameter meaning beyond schema descriptions.

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 it creates a reusable process definition for automated workflows, distinguishing it from sibling tools like update_definition, delete_definition, and execute_task.

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?

Explicitly says to use with process tasks (task_type='process'), providing clear context. Lacks explicit exclusions or alternatives, but is adequate.

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/mstang/casemgr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server