Skip to main content
Glama

deployment_create

Deploy BPMN or DMN artifacts to Operaton by supplying XML content, filename, and deployment name; returns deployment ID and deployed definition keys.

Instructions

Deploy a BPMN or DMN artifact to Operaton. Provide the XML content, filename (.bpmn or .dmn), and a deployment name. Returns deployment ID and deployed definition keys.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "deployment-name": "<deployment-name>",
      "bpmn-content": "<bpmn-content>"
    },
    "name": "deployment_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant-idNoTenant ID for multi-tenant deployments
bpmn-contentYesBPMN 2.0 XML content as a string
bpmn-filenameNoFilename for the BPMN resource (default: process.bpmn)
deployment-nameYesName for this deployment (e.g. 'loan-approval-v2')
deployment-sourceNoSource identifier for this deployment (e.g. 'git', 'manual')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.3.0
    • addedInput schema / properties / bpmn-content
      Added value: +{
      +  "description": "BPMN 2.0 XML content as a string",
      +  "type": "string"
      +}
    • addedInput schema / properties / bpmn-filename
      Added value: +{
      +  "description": "Filename for the BPMN resource (default: process.bpmn)",
      +  "type": "string"
      +}
    • addedInput schema / properties / deployment-name
      Added value: +{
      +  "description": "Name for this deployment (e.g. 'loan-approval-v2')",
      +  "type": "string"
      +}
    • addedInput schema / properties / deployment-source
      Added value: +{
      +  "description": "Source identifier for this deployment (e.g. 'git', 'manual')",
      +  "type": "string"
      +}
    • addedInput schema / properties / tenant-id
      Added value: +{
      +  "description": "Tenant ID for multi-tenant deployments",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "deployment-name",
      +  "bpmn-content"
      +]
  2. First observedv1.1.0

TDQS

A3.5/5.0
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 does disclose that this is a mutation and what it returns (deployment ID and definition keys), but says nothing about idempotency, whether an existing deployment with the same name is rejected or overwritten, or auth requirements.

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?

Three short sentences with the action front-loaded, followed by required inputs and the return shape. No filler, though the DMN mention adds ambiguity rather than value given the bpmn-only parameters.

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?

With no output schema, the description usefully states the return values, and all five parameters are covered by the schema. The remaining gap is the unresolved DMN story: no DMN-specific parameter exists, so an agent cannot tell whether DMN XML belongs in bpmn-content or whether decision_deploy should be used instead.

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 every parameter is already documented, including tenant-id, deployment-source, and the default filename. The description adds only the filename-extension constraint (.bpmn or .dmn) and confirms which values are mandatory, which is marginal added value.

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?

States a specific verb and resource ('Deploy a BPMN or DMN artifact to Operaton') and names the inputs and return values, so the agent knows this creates a new deployment. It does not explicitly separate itself from deployment_redeploy or decision_deploy, and the DMN claim is only partially supported by the bpmn-* parameters.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description tells the agent what to supply, which suggests a create-new-deployment operation. There is no guidance on when to prefer deployment_redeploy or decision_deploy, nor any prerequisite (permissions, tenant, duplicate-name behavior).

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

Deploy Server

Other Tools