Skip to main content
Glama

decision_getXmlByKey

Retrieve the DMN XML for the latest version of a decision definition by key to inspect and verify the current decision table logic.

Instructions

Retrieve the DMN XML of the latest version of a decision definition by key. Use to inspect the current decision table logic.

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_getXmlByKey"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does convey two useful facts: the payload is DMN XML (not JSON metadata) and it targets the latest version rather than a specific one. It omits whether the call is read-only (implied but unstated), what happens if the key is unknown or the definition has no deployed XML, and whether the response includes referenced decision requirements.

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 short sentences, front-loaded with the retrieval semantics and followed by the use case. Nothing is redundant and nothing could be trimmed without losing information.

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?

For a one-parameter read tool with no output schema, the description covers what is returned (DMN XML), which version (latest), and the identifying input. Only error/failure behavior and key format are missing, which are minor for a simple lookup.

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 description coverage is 0% for the single 'key' parameter, so the description must clarify it, and 'of a decision definition by key' does establish that the key identifies a decision definition rather than an instance or deployment. It does not say what form the key takes (generated id string vs. numeric) or whether it corresponds to the key exposed by decision_list/decision_getByKey, leaving a gap for the caller.

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 ('Retrieve the DMN XML of a decision definition') plus a scope qualifier ('latest version'), which meaningfully distinguishes it from a plain decision_getByKey that would return metadata rather than XML. It does not explicitly name the sibling processDefinition_getXmlByKey to clarify the resource boundary (decision vs. process), but the resource is unambiguous on its own.

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?

'Use to inspect the current decision table logic' implies the intended context, so an agent can infer that this is the tool for reading decision logic. There are no exclusions, no mention of when to prefer decision_getByKey or decision_evaluate instead, and no prerequisites 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