Skip to main content
Glama

get_agent_execution_trace

Read-only

Retrieve an ordered timeline for a Now Assist/Otto AI agent run using its execution plan sys_id, including tasks, messages, and tool call request/response details for debugging.

Instructions

Get an ordered timeline for one Otto / Now Assist AI agent run: the execution plan (sn_aia_execution_plan) plus its tasks (sn_aia_execution_task), conversation messages (sn_aia_message) and tool calls with request/response (sn_aia_tools_execution). Use list_ai_agent_executions to find the plan sys_id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per child table (default 200)
include_payloadsNoInclude full tool request/response and message bodies (default false, truncated to 500 chars)
execution_plan_sys_idYessys_id of the sn_aia_execution_plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real value by disclosing that the response is an ordered, multi-table aggregation (plan + tasks + messages + tool calls), which no structured field conveys. It stops short of describing ordering semantics across tables or how limit applies per child table.

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 sentences, zero waste: the first defines the return content, the second handles the routing prerequisite. The scope-defining information is front-loaded.

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 carries the burden of explaining return content, and it does so by naming the four constituent record types and their tables. Slightly incomplete in that the shape of the aggregated result (nesting, ordering) is not described.

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%, and both optional parameters (limit, include_payloads) already document defaults and truncation in the schema. The description adds no parameter-level meaning beyond what is structured, so baseline 3 applies.

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?

States a specific verb (get) and a precisely scoped resource: an ordered timeline for one Otto / Now Assist agent run, enumerated as plan, tasks, messages, and tool calls with the backing tables named. This is clearly distinguishable from aggregate listings such as list_ai_agent_executions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly tells the agent to use list_ai_agent_executions to obtain the plan sys_id, which is exactly the prerequisite an agent would otherwise fumble. No when-not-to-use conditions are given, but the tool's scope is narrow enough that this is a minor gap.

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