Skip to main content
Glama

remove_string_table_entry

DestructiveIdempotent

Delete an entry key and its metadata from a UStringTable asset within an undo transaction and save it; absent keys are treated as already removed.

Instructions

Remove the entry key, with all its metadata, from a UStringTable asset inside an undo transaction, then mark the asset dirty and save it. Idempotent: a key that is not in the table is already the state asked for, so the call succeeds with removed false and already_absent true and changes and saves nothing. A missing table is an error, and so is a failed save, which keeps the removal in memory. Use remove_string_table_metadata to drop only metadata, set_string_table_entry to add or change an entry, get_string_table_entries to list them.

Returns: { string_table_path: string, key: string, removed: bool, existed: bool, already_absent: bool, verified: bool, namespace: string, entry_count: int, saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesEntry key to remove
string_table_pathYesFull asset path to the UStringTable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds substantial context beyond them: the undo transaction wrapper, asset-dirty-and-save behavior, the precise idempotent no-op semantics with resulting flag values, and the partial-failure case where a failed save leaves the removal in memory. This is far richer than the annotations.

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 idempotency, then failure modes, then sibling routing. The trailing Returns block is dense but justified since no output schema exists. No wasted sentences.

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?

A destructive mutation with no output schema is fully covered: the description supplies the return shape, the failure semantics, and the idempotent contract, complementing annotations that already carry the safety profile. Nothing an agent needs 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%, so both parameters are already documented in the schema. The description clarifies what 'key' means semantically (entry key including its metadata) but adds no format or syntax detail beyond the schema. Baseline 3 applies when the schema carries the load.

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 ('Remove the entry key... from a UStringTable asset') and qualifies it by distinguishing the operation from remove_string_table_metadata, set_string_table_entry, and get_string_table_entries by name. An agent can separate this from sibling string-table tools 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 Guidelines5/5

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

Explicitly names the alternatives and the condition that selects each: metadata-only removal, add/change, and listing. It also states when it is a no-op (key already absent) versus an error (missing table, failed save), which is exactly the routing information an agent needs.

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