Skip to main content
Glama

create_data_table

Idempotent

Creates a DataTable asset bound to an existing row struct so designers can edit items, loot, quests, or dialogue without Blueprints.

Instructions

Create a DataTable asset bound to a row struct -- the standard container for game data (items, recipes, loot, quests, dialogue) that designers edit without touching Blueprints. The row struct must already exist (create_struct) and cannot be changed afterwards without losing data, so settle its columns first. Idempotent: re-running with the same row_struct returns the existing table with already_existed instead of erroring. Rows go in with add_data_table_row or import_data_table_csv; create_composite_data_table is the variant that merges several parent tables.

Returns: { table_name, package_path, row_struct, table_path, success, saved, already_existed, message }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
row_structYesName of the UScriptStruct that defines the row structure.
table_nameYesName of the new DataTable.
package_pathNoTarget content package path where the asset is created (check the body for the default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: idempotency semantics (returns existing table with already_existed rather than erroring), the irreversibility warning that the row struct cannot change without data loss, and the full return payload. This goes well past the readOnly/destructive/idempotent hints.

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 core action, then prerequisites, idempotency, and alternatives in descending priority, closing with a compact return shape. Dense but every sentence carries information an agent needs.

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 creation tool with no output schema, it supplies the prerequisite chain, idempotency behavior, sibling alternatives, and an inline description of the return fields. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning to row_struct (must pre-exist, immutable without data loss) that the schema's one-liner does not convey. table_name and package_path are left to the schema, which already documents them.

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+resource ('Create a DataTable asset bound to a row struct') and immediately explains the object's role in the project (game data container). It also differentiates from siblings by naming create_composite_data_table as the merging variant, so an agent can tell them apart without opening schemas.

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?

Explicit prerequisites ('row struct must already exist (create_struct)') and explicit alternatives for follow-up work ('Rows go in with add_data_table_row or import_data_table_csv'). The when-to-use-this-vs-sibling routing to create_composite_data_table is spelled out.

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