Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_asset_jobs

List Asset Processor jobs for a source file, including status, counts, and failure logs, to diagnose build or processing issues.

Instructions

List the Asset Processor jobs for one source file, with failure logs.

Returns {"source_path", "jobs": [{"job_key", "platform", "builder", "status", "error_count", "warning_count", "job_run_key", "source_file", "watch_folder", "log"?, "truncated"?}]} with status one of queued, in_progress, failed, completed or missing. A source the Asset Processor has not registered answers the error code engine_error. Needs the AiCompanion gem 0.6.0+; works in secure mode.

Args: source_path: The source file, relative to the project or a full path. escalate: Move the file's queued jobs to the front of the queue. include_logs: Attach each failed job's log (cut at 64 KB).

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

Input Schema

NameRequiredDescriptionDefault
escalateNo
source_pathYes
include_logsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burdens, and it discloses a lot: the engine_error code returned for unregistered sources, the AiCompanion gem 0.6.0+ prerequisite, and secure-mode compatibility. It does not flag that escalate mutates queue ordering or that include_logs truncates logs, but overall the behavioral disclosure is strong.

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?

The purpose is front-loaded in the first sentence and the Args block is tight and well-organized. The return-structure block is somewhat redundant since a consumed output schema already exists, but the overall length is reasonable and every section is legible.

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?

For a 3-parameter read tool with an output schema, the description covers purpose, prerequisites, error behavior, enum values, and per-parameter semantics. Nothing an agent needs to select or invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it explains source_path accepts a project-relative or full path, escalate moves queued jobs to the front of the queue, and include_logs attaches failed-job logs truncated at 64 KB. All three parameters gain meaning beyond their bare titles.

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 first sentence states a specific verb and resource with scope: listing Asset Processor jobs for one source file, including failure logs. It is clear enough to distinguish from broad siblings like get_asset_processor_status, but it never explicitly names or contrasts those siblings, so it stops short of a 5.

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 when-to-use guidance or routing against alternatives such as get_asset_status, wait_for_asset, or get_asset_processor_status. The agent must infer from the description alone that this is the tool for per-file job inspection, and there are no exclusions or preconditions stated beyond a passing gem-version note.

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