Skip to main content
Glama
CRACKISH

mcp-creatio

by CRACKISH

Execute Creatio Business Process

execute-process

Triggers a Creatio CRM business process by supplying its schema name and key-value parameters. Executes server-side workflows with input data.

Instructions

Execute a Creatio CRM business process with optional parameters. This tool runs server-side business processes in Creatio platform.

WORKFLOW FOR LLM:

  1. If user provides display name/caption (e.g., "Lead Qualification Process"):

    • First use "read" tool on VwProcessLib entity

    • Filter: contains(Caption,'user_provided_name')

    • Select: ["Name", "Caption"]

    • Use the "Name" field value as processName parameter

  2. If user provides schema name directly (e.g., "UsrLeadQualificationProcess"):

    • Use it directly as processName parameter

Process Identification:

  • This tool accepts ONLY schema names (e.g., "RunActualizeProcess")

  • Schema names are technical identifiers stored in VwProcessLib.Name column

  • Display names/captions are user-friendly names in VwProcessLib.Caption column

Parameters:

  • Passed as object with key-value pairs

  • Parameter names typically start with uppercase letter

  • Supports all JSON types: strings, numbers, booleans, GUIDs

Common Parameter Patterns:

  • Entity IDs: ContactId, AccountId, OpportunityId, LeadId, CaseId

  • Amounts: Amount, Price, Sum, Cost

  • Text fields: Description, Notes, Text, Comment, Title

  • Flags: IsActive, IsCompleted, SendEmail, CreateActivity

  • Dates: StartDate, EndDate, DueDate (ISO format)

GUID & Date Helpers: /datetime-guide prompt applies to EVERY date/time parameter (convert to UTC). /contactid-guide prompt applies to EVERY user/contact participant parameter (OwnerId, AuthorId, AssigneeId, ResponsibleId, CreatedById overrides, etc).

Example: { "processName": "Lead Management Process", "parameters": { "ContactId": "2ad0270b-dc4c-4fbf-9219-df32ce4c34fc", "Amount": 15000, "Description": "High priority lead", "SendNotification": true } }

Uses Creatio ProcessEngineService.svc/Execute endpoint for execution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoParameters to pass to the business process as key-value pairs. Parameter names typically start with uppercase letter. Examples: - ContactId: "2ad0270b-dc4c-4fbf-9219-df32ce4c34fc" (GUID values) - Amount: 1000 (numeric values) - Text: "SomeText" (string values) - BoolParam: true (boolean values) Common parameter patterns: ContactId, AccountId, OpportunityId, Amount, Description, etc.
processNameYesREQUIRED: Schema name of the Creatio business process (e.g., "RunActualizeProcess"). IMPORTANT: This parameter accepts ONLY schema names, NOT display names/captions. If user provides a display name/caption (e.g., "Actualize Process"), you MUST first use the "read" tool to find the corresponding schema name in VwProcessLib table: - Use filter: contains(Caption,'user_provided_name') - Select fields: ["Name", "Caption"] - Use the "Name" field value as processName parameter.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool runs server-side business processes via a specific endpoint (ProcessEngineService.svc/Execute). It also explains the process identification steps. However, it does not mention return values, side effects, permissions, or error handling, leaving gaps.

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?

The description is well-structured with clear sections (WORKFLOW FOR LLM, Process Identification, Parameters, etc.). Each sentence adds value. However, it is somewhat lengthy, and the example contains a contradictory use of a display name as processName, which undermines conciseness and clarity.

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

Completeness1/5

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

Without an output schema, the description should explain the return value but does not. More critically, the example uses a display name ('Lead Management Process') as the processName, directly contradicting the explicit rule that only schema names are accepted. This internal contradiction severely reduces completeness and could mislead an AI agent.

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

Parameters5/5

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

Schema coverage is 100% for both parameters. The description adds significant meaning beyond the schema: it explains the workflow for processName (display name to schema name mapping), provides common parameter patterns, GUID/date helpers, and an example. This greatly aids correct parameter construction.

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 clearly states the tool executes a Creatio CRM business process with optional parameters. It distinguishes from sibling CRUD and configuration tools by focusing on server-side process execution. The verb 'execute' and resource 'business process' are specific.

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 provides a detailed workflow for LLM on how to handle display names vs schema names, including a step to use the 'read' tool. While it doesn't explicitly state when not to use this tool, it gives strong procedural context. However, it lacks explicit exclusion criteria or comparison to alternatives.

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/CRACKISH/mcp-creatio'

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