Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_project_gems

Find which gems are enabled in an O3DE project by providing its project path, giving you a clear inventory of active gems for project configuration and troubleshooting.

Instructions

List gems enabled in a specific O3DE project.

Args: project_path: Path to the O3DE project.

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": {
      "project_path": "<project_path>"
    },
    "name": "list_project_gems"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations available, the description carries the behavioral burden. 'List' indicates a read-only operation scoped to a specific project, but it discloses no further traits such as side effects, error behavior, or whether the project must be active.

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?

The description is compact and front-loaded: the core behavior is stated in the first sentence, and the only parameter is documented in one clear line. No superfluous text is present.

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 listing tool with an output schema present, the description covers the essential call details: what it returns conceptually and what the project_path argument means. It is slightly incomplete in not addressing the relationship to sibling listing tools, but nothing critical is missing for a straightforward invocation.

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?

Schema description coverage is 0%, so the description must define the parameter. It does so with 'project_path: Path to the O3DE project,' which adds meaning beyond the raw string type and title, though it leaves format details unspecified.

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 states a specific action and object: 'List gems enabled in a specific O3DE project.' It clearly identifies the tool's scope, distinguishing it from a generic gems listing, though it does not explicitly name or contrast sibling list_gems.

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?

The description gives no guidance about when to choose this tool over alternatives. It does not mention list_gems, enable_gem, or disable_gem, and it does not state conditions or prerequisites such as requiring an existing project.

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