Skip to main content
Glama

create_gameplay_tag

Destructive

Add and register a gameplay tag in the current Unreal Editor session before using it in DataTable rows or properties; unregistered tags silently reset to None.

Instructions

Add a new gameplay tag to the project's DefaultGameplayTags.ini AND register it LIVE in this editor session -- that live half is why you must call this before writing the tag into a DataTable row or a property, since an unregistered tag string is silently reset to None by the importers. But it REWRITES THE WHOLE INI: the list comes back alphabetised, every comment block is deleted, and other tags' DevComments are re-serialised and normalised, so adding one tag can produce a diff full of unrelated insertions and deletions. Copy the ini first; the oracle is git diff --stat showing your N insertions and ZERO deletions, and if not, git checkout the ini and re-insert only your line (the tag stays registered live either way -- confirm with find_gameplay_tag).

Returns: { tag_name: string, success: bool, tag_string: string, message: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tag_nameYesName of the gameplay tag to create or check
dev_commentNoOptional developer comment for the tag
source_nameNoOptional explicit source INI name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Discloses far more than the annotations: it REWRITES THE WHOLE INI, alphabetises the list, deletes comment blocks, and re-serialises other tags' DevComments. It also documents the recovery procedure and the diff-based oracle, all consistent with destructiveHint=true and non-idempotent behavior.

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-loads the core action and the live-registration caveat before the destructive warning, so the most important content is first. It is dense and somewhat run-on with parenthetical asides, but nearly every clause carries actionable 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?

For a destructive mutation tool with no output schema, the description supplies the return shape inline ({tag_name, success, tag_string, message}) plus the destructive-write consequences and recovery path. Nothing needed to call it safely is missing.

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 coverage is 100%, so tag_name, dev_comment and source_name are already documented in the schema. The description adds only tangential meaning (mentioning DevComments get re-serialised) and does not clarify source_name or dev_comment semantics beyond the schema.

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 gameplay tag) and precisely scopes the dual effect: writing DefaultGameplayTags.ini AND registering it live in the editor session. This distinguishes it from siblings like add_gameplay_tag_to_table and add_gameplay_tag_redirect without the agent needing to open another 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?

Gives an explicit ordering rule ('you must call this before writing the tag into a DataTable row or a property') with the consequence of failure (silent reset to None), and names find_gameplay_tag as the verification alternative. Both the when and the fallback are stated.

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