Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_gem

Create a new O3DE gem in a specified directory using a chosen template. Provide a name and path to scaffold the gem project.

Instructions

Create a new O3DE gem.

Args: name: Gem name (alphanumeric, hyphens, underscores). path: Directory where the gem will be created. template: Gem template to use (default: DefaultGem).

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": {
      "name": "<name>",
      "path": "<path>"
    },
    "name": "create_gem"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
pathYes
templateNoDefaultGem

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It states that a new gem is created and takes a path, implying filesystem writes, but it does not mention side effects, overwrite behavior, template resolution, or any permissions needed. This is minimal for a creation tool with no annotation safety hints.

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 description is short, front-loaded with the one-sentence purpose, and uses a compact argument list. There is no filler, though the argument documentation is terse and could integrate more context without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple create operation, the description covers the required parameters (name, path) and the optional template with default. An output schema exists, so return values need not be described. However, without annotations, it lacks any note about side effects or prerequisites, leaving some behavioral context incomplete.

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?

The input schema has 0% description coverage, so the description must compensate. It does add meaning: name constraints (alphanumeric, hyphens, underscores), path as the target directory, and template with a default. This is useful but not rich; valid template values and path forms are not clarified.

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?

The description states a specific verb and resource: 'Create a new O3DE gem.' The word 'new' clearly distinguishes this from sibling tools like register_gem or list_gems, so an agent can recognize what operation is intended.

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 guidance on when to use this tool versus alternatives such as register_gem, list_gems, or create_project. The description explains what the tool does but does not specify the context or exclude cases where another sibling would be more appropriate.

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