Skip to main content
Glama

create_directory

Idempotent

Creates a Content Browser folder at a UE long path so you can lay out system folders before adding assets; existing paths return already_existed:true, not an error.

Instructions

Make a content-browser folder at a UE long path (e.g. /Game/MyGame/Systems/Foo). Idempotent: an existing folder is not an error, it comes back already_existed:true. Use it to lay out a system's folders before creating assets there; a path that does not start with '/' is rejected.

Returns: { path: string, already_existed: bool (true = nothing was created, and that is a success) }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoUE long path of the folder to create, e.g. /Game/MyGame/Systems/Foo. Must start with '/', not a disk path.
asset_pathNoAlias of `path` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `path`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, but the description adds the concrete idempotency contract (existing folder returns already_existed:true and is a success, not an error) plus the input rejection rule for paths not starting with '/'. That is real behavioral detail beyond the structured flags, though it doesn't touch permissions or side effects on parent folders.

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?

Front-loaded with the purpose and example, then idempotency, then usage guidance, then the return shape. Four tight sentences with no filler, each carrying distinct information.

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?

No output schema exists, yet the description supplies the return shape (path, already_existed with its success semantics) on top of idempotency and validation rules. For a 2-param, low-complexity creation tool this is complete.

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%, so both parameters including the asset_path alias are already documented in the schema; the description's path example and '/' prefix rule largely restate what the schema says. It never mentions the asset_path alias, so it adds no meaning beyond the schema – baseline 3 is appropriate.

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 (create a content-browser folder) with an example UE long path that makes the target unmistakable, and scopes it to the content browser rather than the OS filesystem. An agent can tell this apart from sibling creation tools like create_collection or create_usd_stage without opening any schema.

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

Usage Guidelines4/5

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

"Use it to lay out a system's folders before creating assets there" gives clear when-to-use context. However, it never names an alternative or a when-not-to-use condition, so the routing signal to related siblings such as duplicate_directory or delete_directory is left 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