Skip to main content
Glama

decision_getByKey

Fetch the current deployed version of a decision definition by key, returning its key, ID, version, and deployment details for Operaton process decisions.

Instructions

Retrieve the latest deployed version of a decision definition by its key. Returns key, id, version, and deployment details.

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

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

B3.3/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden. It names the returned fields (key, id, version, deployment details), which is useful, but says nothing about permissions, error behavior when the key is unknown or unversioned, or whether non-latest versions are ever returned.

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?

Two short sentences with the retrieval action and scope front-loaded, followed by the return summary. Nothing is padded, though the return sentence could carry slightly more decision-relevant detail for the same length.

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 lookup with no output schema and no annotations, the description is reasonably complete: it establishes the input meaning, the resolved version semantics, and the shape of the return. Missing failure-mode context is a modest gap given the tool's simplicity.

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?

The single parameter has 0% schema description coverage, so the description must compensate. "By its key" confirms the key identifies the decision definition and that the latest deployed version is resolved implicitly, but gives no format, case-sensitivity, or uniqueness detail.

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 uses a specific verb and resource ("Retrieve the latest deployed version of a decision definition") and adds the scoping qualifier "latest deployed version," which separates it from id-based and XML variants in the sibling set. It doesn't explicitly name a sibling, but the key-vs-id and definition-vs-XML distinctions are inferable.

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?

Usage is only implied: an agent can infer that this is the tool to call when it holds a decision key and wants the newest deployed version rather than the XML or an id-addressed lookup. There is no explicit when-to-use, when-not-to-use, or named alternative.

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