Skip to main content
Glama

add_socket_to_skeleton_asset

Add or update a named socket on a USkeleton bone (root by default) at a bone-relative location and rotation, then save the asset.

Instructions

Add a socket to a USkeleton asset on a bone (the root by default) at a bone-relative location and rotation, then save; an existing socket of that name is updated in place (already_existed true). A failed save makes success false, with saved=false and save_error. A socket on a skeletal mesh asset (copied to its skeleton when that skeleton is project content): add_skeletal_mesh_socket.

Returns: { asset_path: string, socket_name: string, bone_name: string, socket_count: int, added: bool, already_existed: bool, saved: bool, save_error: string? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoSocket location relative to its bone as [x, y, z] (default 0,0,0)
rotationNoPREFERRED: the OBJECT {"roll":R,"pitch":P,"yaw":Y} (any subset, absent axes are 0). The ARRAY form below is [pitch, yaw, roll] -- its index 2 is ROLL, NOT yaw, which once put a PlayerStart on its side. Socket rotation relative to its bone as [pitch, yaw, roll] (default 0,0,0)
bone_nameNoBone to attach the socket to; must exist in the skeleton (default the root bone).
socket_nameYesName of the socket; an existing socket with this name is updated instead of duplicated.
skeleton_pathYesUSkeleton asset path, e.g. "/Game/Characters/SK_Hero_Skeleton".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / bone_name / description
      Previous value: -"Bone to attach the socket to, defaults to root bone"New value: +"Bone to attach the socket to; must exist in the skeleton (default the root bone)."
    • changedInput schema / properties / skeleton_path / description
      Previous value: -"Path to the USkeleton asset"New value: +"USkeleton asset path, e.g. \"/Game/Characters/SK_Hero_Skeleton\"."
    • changedInput schema / properties / socket_name / description
      Previous value: -"Name for the new socket"New value: +"Name of the socket; an existing socket with this name is updated instead of duplicated."
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds real behavioral detail beyond them: the asset is saved, an existing same-named socket is updated in place, and a failed save yields success=false with saved=false and save_error. The 'updated in place' wording sits somewhat in tension with idempotentHint=false, but that is a minor nuance rather than a hard read/write or destructive contradiction.

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 default, then the update/save behavior, then the sibling routing, ending with a compact returns object. Dense but every clause carries information; no filler 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?

For a mutation tool with no output schema, the description embeds the return shape (asset_path, socket_name, bone_name, socket_count, added, already_existed, saved, save_error), plus save-failure semantics and the alternative tool. Nothing an agent needs to call and interpret the result 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 the schema already documents location (bone-relative), rotation, bone_name (root default), socket_name (update-in-place), and skeleton_path. The description restates the bone-relative/default-bone and update-in-place semantics but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Add a socket to a USkeleton asset on a bone'), including the default (root bone) and the save step. It explicitly distinguishes itself from the sibling add_skeletal_mesh_socket, so an agent can route correctly without opening either 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?

Names the alternative tool add_skeletal_mesh_socket and the condition that selects it (sockets on a skeletal mesh asset), which is strong routing guidance. It does not, however, state preconditions or when this tool is the wrong choice within its own domain (e.g., that the skeleton must be an editable project asset).

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