Skip to main content
Glama

trace_table_operation

Read-only

Map every stage of a ServiceNow table operation—ACLs, business rules, database writes, notifications, workflows, and inherited rules—with record links and a Mermaid diagram. Read-only.

Instructions

Everything that runs for one operation on a table, in order: ACLs (Deny Unless first), before business rules, the database write, after business rules, assignment rules, SLA definitions, notifications, Flow Designer record triggers, legacy workflows, and async business rules. Includes rules inherited from parent tables (for example task for incident), links to each record, and a Mermaid diagram. Read-only

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

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, e.g. incident
operationNoOperation to trace (default update)
max_per_stageNoMax items listed per stage (default 20). The summary always counts them all
include_inactiveNoAlso list inactive items (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real substance: the precise stage ordering, that rules inherited from parent tables (e.g., task for incident) are included, that each record is linked, and that a Mermaid diagram is produced. The trailing "Read-only" merely restates the annotation, and no cost/performance caveat is given for an open-world query.

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?

Front-loaded with the core idea (everything that runs, in order) followed by a compact enumeration of stages. The long stage list earns its place as the tool's substance, though the dangling "Read-only" sentence adds nothing beyond annotations.

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?

With no output schema, the description does the work of explaining return content: ordered stages, inherited rules, per-record links, and a Mermaid diagram. For a read-only diagnostic tool with fully documented parameters, this is nearly sufficient; only guidance on interpretation and expected runtime is absent.

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%, with defaults, enum values, and the note that the summary always counts all items already documented in the schema. The description adds no parameter-level meaning beyond noting inherited parent-table rules, 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 enumerates exactly what the tool returns: the ordered set of server-side stages executed for one table operation (ACLs, business rules, database write, workflows, etc.), which is highly specific and clearly separable from siblings like get_agent_execution_trace or check_table_completeness. It never states the verb "trace" explicitly and names no siblings, so it is clear but lacks explicit differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is mentioned. An agent must infer that this is for diagnosing execution order on a table rather than for completeness checks or generic agent traces.

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