Skip to main content
Glama

get_ai_agent_execution

Read-only

Retrieves an AI Agent execution plan and its step-by-step tool calls from execution plan and task records, given a plan sys_id, so you can inspect how an agent ran.

Instructions

Get an AI Agent execution plan with its steps/tool calls (sn_aia_execution_plan + sn_aia_execution_task)

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

Input Schema

NameRequiredDescriptionDefault
sys_idYessys_id of the execution plan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.15.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real context by disclosing the returned payload (steps/tool calls) and the source tables, but says nothing about permissions, result size, or whether missing/expired plans error or return empty.

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?

A single front-loaded sentence with no filler; the parenthetical table names are the only slightly cryptic element but they do add informational value about where the data lives.

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-only getter with no output schema, the definition covers the essentials: what entity is fetched and what the response contains. It is only marginally incomplete in not contrasting itself with the sibling trace tool.

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% for the single sys_id parameter, so the schema already explains it. The description only reinforces that the id refers to an 'execution plan'; it adds no format, sourcing, or lookup guidance beyond the schema, which is the expected baseline here.

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 names a specific verb and resource ('Get an AI Agent execution plan') and clarifies that the result includes steps/tool calls, plus the underlying tables. It does not, however, distinguish itself from the closely named sibling get_agent_execution_trace, leaving the boundary between plan retrieval and trace retrieval implicit.

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 guidance on when to use this tool versus get_agent_execution_trace or list_ai_agent_executions. The agent must infer from the name and from the required sys_id that this is a detail lookup by plan identifier.

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