Skip to main content
Glama

decisionRequirements_list

List deployed Decision Requirements Definitions (DRDs) to inspect dependencies between decision tables in complex DMN models, with filters for name, key, version, tenant, and deployment.

Instructions

List deployed Decision Requirements Definitions (DRDs). DRDs describe dependencies between decision tables in a complex DMN model.

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": "decisionRequirements_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
nameNo
sortByNo
keyLikeNo
versionNo
categoryNo
nameLikeNo
sortOrderNo
maxResultsNo
tenantIdInNo
firstResultNo
categoryLikeNo
deploymentIdNo
resourceNameNo
latestVersionNo
withoutTenantIdNo
resourceNameLikeNo
decisionRequirementsDefinitionIdNo
decisionRequirementsDefinitionIdInNo
includeDecisionRequirementsDefinitionsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv1.3.0
    • addedInput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / categoryLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionRequirementsDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / decisionRequirementsDefinitionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deploymentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / includeDecisionRequirementsDefinitionsWithoutTenantId
      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 / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure. It implies a read-only listing of deployed DRDs, but does not state pagination, filtering behavior, permissions, return format, or how the 20 parameters affect results.

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

Conciseness5/5

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

Two front-loaded sentences with no filler; the definition sentence earns its place by explaining DRDs. It is appropriately sized for a simple description, though it is under-informative rather than verbose.

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?

For a 20-parameter list tool with no annotations and no output schema, the description is far too thin. It identifies the resource but does not explain how to filter, sort, page, or what a call returns.

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

Parameters1/5

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

Schema description coverage is 0% for 20 parameters, and the description mentions none of them. It adds no meaning about key, name, version, tenant, sorting, or pagination parameters.

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 (List) and resource (Decision Requirements Definitions), and the 'deployed' scope narrows it. The second sentence defines DRDs, helping distinguish them from decision tables, but the description does not explicitly compare against sibling tools such as decision_list.

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 when-to-use guidance, no alternatives, no exclusions. An agent must infer that this is the tool for listing DRDs rather than decisions or deployments.

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