Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_asset_processor_connection

Check if the O3DE editor is connected to the Asset Processor and measure ping latency, helping diagnose editor-side connectivity issues via AiCompanion.

Instructions

Report whether the editor is connected to the Asset Processor.

Returns {"connected", "ping_ms"}. Unlike get_asset_processor_status, which checks for the process on this machine without the editor, this asks the editor itself. Needs the AiCompanion gem 0.6.0+.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_asset_processor_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, so the description carries the burden, and it does add real context: the return payload shape and, importantly, the prerequisite 'Needs the AiCompanion gem 0.6.0+'. It does not describe failure behavior when the gem is absent or when the connection is down, so it falls just short of full disclosure.

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 purpose, then the return shape, then the sibling contrast, then the prerequisite. Tight and well ordered, though the inline return-field listing partially duplicates the existing output schema.

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?

Given an output schema already documents the return values, the description supplies exactly the missing pieces: the sibling disambiguation and the gem version prerequisite. Nothing an agent needs to call it correctly is absent.

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

Parameters4/5

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

Zero parameters, so the baseline of 4 applies. The description correctly adds no parameter detail because none exist.

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 and resource ('Report whether the editor is connected to the Asset Processor') and explicitly names the sibling it must not be confused with (get_asset_processor_status), explaining the semantic difference. An agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Explicitly distinguishes this tool from the alternative: get_asset_processor_status checks the process on the machine, whereas this asks the editor itself. The selecting condition is stated, leaving nothing to inference.

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