Skip to main content
Glama

get_data_table_row

Read-onlyIdempotent

Read one DataTable row by key and return all columns as JSON. Works for Blueprint or user-defined row structs where typed lookups report missing rows.

Instructions

Read ONE row of a DataTable by key and get every column as JSON . Reads the row memory untyped (FindRowUnchecked), so it works on Blueprint / user-defined row structs that are not FTableRowBase children, where the typed lookup reports "Row not found" for rows that exist; a miss here really is a missing key. Serializes TMap, nested struct and GameplayTag columns. When you need the byte-exact ExportText of a column (to copy a vendor row, or to tell an empty enum from an unwritten one) use read_data_table_row_complex instead, and get_data_table_rows when you want the enum DISPLAY names.

Returns: { table_path, row_name, row_data } where row_data is the fully serialized row struct (TMap / nested struct / FGameplayTag columns included)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
row_nameYesThe name of the row to retrieve.
table_pathYesThe full asset path to the DataTable.

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?

Annotations already cover the read-only/idempotent safety profile, and the description adds substantial context beyond them: the untyped FindRowUnchecked read path, the semantics of a 'Row not found' result (a miss here really is a missing key), and that TMap / nested struct / GameplayTag columns are serialized. This is genuine behavioral disclosure, not restatement.

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 purpose then adds caveats, alternatives, and return shape in a logical order, with each sentence carrying real information. Some sentences are long and clause-heavy, but almost nothing is filler except the near-redundant returns note.

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?

With no output schema, the description supplies the return shape ({ table_path, row_name, row_data }) as well as the serialization caveats an agent needs. Combined with explicit sibling routing, nothing required 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for both parameters (table_path, row_name), so the schema already carries the parameter documentation. The description implies keyed lookup semantics but adds no format or syntax detail beyond what the schema provides; 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 precise verb and resource ('Read ONE row of a DataTable by key') and specifies what is returned ('every column as JSON'). It explicitly distinguishes itself from read_data_table_row_complex and get_data_table_rows, so an agent can select it without opening sibling 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 routing: use read_data_table_row_complex when byte-exact ExportText is needed, and get_data_table_rows when enum DISPLAY names are wanted. It also names the condition under which this tool is uniquely correct (untyped lookup on non-FTableRowBase structs where typed lookup falsely reports 'Row not found').

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