Skip to main content
Glama

decision_list

List deployed DMN decision definitions and filter by key, name, version, or tenant to retrieve decision keys, IDs, versions, and deployment details.

Instructions

List deployed DMN decision definitions. Filter by key, name, version, or tenant. Returns decision key, id, version, and deployment info.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "decision_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
nameNo
sortByNo
keyLikeNo
versionNo
categoryNo
nameLikeNo
sortOrderNo
deployedAtNo
maxResultsNo
tenantIdInNo
versionTagNo
firstResultNo
categoryLikeNo
deploymentIdNo
resourceNameNo
deployedAfterNo
latestVersionNo
versionTagLikeNo
withoutTenantIdNo
resourceNameLikeNo
decisionDefinitionIdNo
decisionDefinitionIdInNo
decisionRequirementsDefinitionIdNo
decisionRequirementsDefinitionKeyNo
withoutDecisionRequirementsDefinitionNo
includeDecisionDefinitionsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed27 schema fields changedv1.3.0
    • addedInput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / categoryLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionDefinitionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionRequirementsDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionRequirementsDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deployedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deployedAt
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deploymentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / includeDecisionDefinitionsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / keyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / latestVersion
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / resourceName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / resourceNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / version
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / versionTag
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / versionTagLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / withoutDecisionRequirementsDefinition
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosing behavior, yet it omits pagination, default sorting, permissions/read-only status, and tenant-scoping semantics. It does mention returned fields, which adds some value, but the behavioral picture remains thin.

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 front-loaded, three sentences, and free of wasted wording. It is arguably too terse given the 27-parameter surface, but structurally it is clean and easy to scan.

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?

This is a highly complex listing tool with 27 parameters, no annotations, no output schema, and no schema descriptions. The description covers only the basic purpose and a few filters, leaving too much unsaid for an agent to invoke it confidently.

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

Parameters2/5

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

There are 27 parameters and 0% schema description coverage, but the description explains only key, name, version, and tenant filtering. It leaves major parameters such as keyLike, latestVersion, tenantIdIn, withoutTenantId, maxResults, firstResult, and sortBy/order unexplained, so it does little to compensate for the schema gap.

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 gives a specific verb and resource: 'List deployed DMN decision definitions,' which clearly separates it from decision_evaluate and decision_getByKey by action. It does not explicitly name sibling alternatives, but the core purpose is unambiguous.

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?

The phrase 'Filter by key, name, version, or tenant' implies the listing/filtering use case, but there is no explicit guidance about when to choose this tool over decision_getByKey or decisionRequirements_list. Usage must largely be inferred.

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