Skip to main content
Glama

decision_evaluate

Evaluate a deployed DMN decision table by key with typed input variables and return the matched rule outputs, so you can test decision logic through AI.

Instructions

Evaluate a deployed DMN decision table by key with typed input variables. Returns the matched rule outputs. Used to test decision logic through AI.

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": {
      "key": "<key>"
    },
    "name": "decision_evaluate"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "key"
      +]
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Since no annotations are present, the description must define the behavior. It clarifies the output is the 'matched rule outputs.' This is useful behavioral disclosure, but it lacks detail on error handling or specific performance characteristics of the evaluation engine.

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 concise and fronts the most critical technical information immediately in the first sentence. The second sentence provides helpful context for intended usage but slightly dilutes the technical focus.

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?

The description is reasonably complete for a tool lacking an output schema. It defines the core action and the result of that action (matched rule outputs). For a complex runtime execution tool, this level of detail is adequate but not exhaustive.

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

Parameters4/5

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

The input schema only explicitly defines the required 'key' parameter. The description significantly adds meaning by stating the tool accepts 'typed input variables,' clarifying that the input payload contains more than just the key.

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 and specifically identifies the action (Evaluate), the resource (DMN decision table), and the input mechanism (by key with typed input variables). This distinguishes it from sibling tools like decision_getByKey, which would only retrieve definitions.

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 tool specifies its use case ('to test decision logic through AI'), which provides contextual guidance. However, it does not explicitly state when *not* to use this tool (e.g., for retrieval or deployment tasks), leaving a minor gap in decision-making criteria.

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