Skip to main content
Glama

process-update_definition

process-update_definition

Modify a process definition by providing its ID and optional fields to change its name, description, execution mode, retry count, timeout, or configuration for agents, automation, or webhooks.

Instructions

Updates a process definition

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_configNoFor ai_agent: {prompt_template, input_items, output_item_type}
automation_configNoFor internal_automation: {operations: [{type, ...}]}
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.
definition_idYesProcess definition ID (@rid format)
descriptionNoWhat this process does
execution_modeNosync or async
nameNoDefinition name
retry_countNoNumber of retries on failure
timeout_secondsNoOverall execution timeout
triggers_sentryNoSentry ID to trigger on successful completion
versionNoVersion string
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 are provided, so the description bears the full burden of behavioral disclosure. It only says 'updates' without mentioning side effects, idempotency, permissions, or error handling, leaving significant gaps.

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

Conciseness3/5

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

The description is extremely concise (one sentence) with no wasted words, but it sacrifices completeness. It is front-loaded but does not earn its place given the complexity of the tool.

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?

With 12 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain return values, error conditions, or usage patterns, leaving the agent underinformed.

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?

The input schema has 100% description coverage, with each parameter clearly documented. The description adds no extra information beyond the schema, so a baseline score of 3 is appropriate.

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?

The description clearly states 'Updates a process definition', specifying the verb and resource. However, it does not distinguish itself from sibling tools like process-create_definition or process-delete_definition, leaving ambiguity about when to use this specific tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives (e.g., create, delete). The description lacks any context for appropriate usage scenarios or exclusions.

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