Skip to main content
Glama

create_decision_table

Create a ServiceNow Decision Builder decision table to define decision logic and answer sources; requires WRITE_ENABLED=true.

Instructions

Create a Decision Builder decision table (sys_decision). Requires WRITE_ENABLED=true

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

Input Schema

NameRequiredDescriptionDefault
nameYesDecision table name
activeNoWhether the decision table is active (default true)
fieldsNoAdditional sys_decision field values to set
descriptionNoDescription of what the decision returns
answer_tableNoTable whose records are the answers (e.g. sys_user_group); needed before the decision can be used

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / answer_table
      Added value: +{
      +  "description": "Table whose records are the answers (e.g. sys_user_group); needed before the decision can be used",
      +  "type": "string"
      +}
  2. Addedv4.15.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the write/safety profile is covered structurally. The description adds real value with the WRITE_ENABLED=true configuration gate, which annotations cannot express. It does not, however, mention what happens on duplicate names (relevant since idempotentHint is false) or what is returned after creation.

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 with the action front-loaded and the environmental prerequisite second; nothing is redundant and no sentence could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description identifies the resource, the persistence table, and the runtime gate, and the schema fully documents all five parameters including the nested 'fields' bag and the answer_table requirement. No output schema exists, but the creation contract is clear enough for an agent to invoke the tool correctly and then look up the new record via get_decision_table.

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 100%, so every parameter — including the open-ended 'fields' object and the 'answer_table' prerequisite — is already documented in the schema with examples. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 states a specific verb and resource — 'Create a Decision Builder decision table (sys_decision)' — and even names the underlying table, which lets an agent distinguish it from get_decision_table, list_decision_tables, and create_decision_input. It stops short of explicitly contrasting with those siblings, but the verb+resource pairing 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Requires WRITE_ENABLED=true' is a precondition rather than usage guidance; it usefully signals when the call will fail, but the description never says when to create a table versus adding inputs or answers, nor does it name any alternative. An agent must infer the workflow ordering (create table → create inputs → publish) from sibling names alone.

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