Skip to main content
Glama

decision_deploy

Deploy DMN decision artifacts to Operaton using DMN XML, a .dmn filename, and a deployment name; returns deployment metadata and decision definition keys.

Instructions

Deploy a DMN decision artifact to Operaton. Provide DMN XML, a .dmn filename, and a deployment name. Returns deployment metadata and deployed decision 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": "decision_deploy"
  }
}

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

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. It does useful work by stating the return value ('deployment metadata and deployed decision definition keys'), but for a mutating deploy operation it omits whether existing deployments are overwritten, whether the call is idempotent, what errors occur on malformed DMN, and what auth/tenant scoping is required.

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, front-loaded with the action and followed by inputs and outputs; no filler. Minor redundancy with schema parameter descriptions, and the numbering of inputs omits tenant-id and deployment-source, but the text is compact and readable.

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

Completeness3/5

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

No output schema exists, and the description compensates by naming what is returned, which is the right call. However, no annotations plus no guidance on overlapping deployment siblings leaves gaps for a mutating tool: duplicate handling, error modes, and the DMN-vs-BPMN field naming ambiguity are all unresolved.

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 the baseline is a 3 and the schema already documents all five parameters. The description does not resolve a real inconsistency it introduces: it calls the payload 'DMN XML' and a '.dmn filename', while the required schema fields are named bpmn-content/bpmn-filename and described as 'BPMN 2.0 XML content', leaving the agent to infer that DMN content goes into the bpmn-* fields.

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?

Clear, specific verb+resource: 'Deploy a DMN decision artifact to Operaton', which distinguishes the artifact type (DMN vs BPMN) from its sibling processDefinition_deploy. It does not, however, distinguish itself from deployment_create or deployment_redeploy, which also deploy resources, so an agent cannot tell from the description alone which deployment entry point to pick.

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?

The description only tells the agent what to supply ('Provide DMN XML, a .dmn filename, and a deployment name'), never when this tool is the right choice over deployment_create, processDefinition_deploy, or deployment_redeploy, nor when not to use it. No prerequisites (permissions, tenant requirements) or duplicate-deployment behavior are stated.

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