Skip to main content
Glama

sharp_equipment_attach

Attaches equipment and props to character rigs, configuring limb slots, IK, animation clips, and export options for Roblox Studio or Blender workflows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sharp_equipment_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
modeNo
slotNo
actionNoattach
detailNosummary
presetNo
ik_typeNoTransform
play_nowNo
rig_pathNoWorkspace.Rig
clip_dataNo
clip_nameNo
fade_timeNo
ik_weightNo
intensityNo
item_pathNoWorkspace.EquipmentItem
limb_partNo
prop_kindNosword
prop_nameNoSharpProp
studio_idNo
clone_itemNo
export_fbxNo
export_glbNo
offset_posNo
output_dirNo
create_poleNo
filter_limbNo
folder_nameNoAnimations
preset_nameNo
auto_installNo
preset_namesNo
sidecar_dataNo
sidecar_pathNo
expected_kindNo
filter_presetNo
rig_spec_pathNo
armor_slot_mapNo
execution_modeNoauto
ik_smooth_timeNo
offset_rot_degNo
required_slotsNo
execute_blenderNo
item_attachmentNo
item_size_studsNo
limb_attachmentNo
rig_height_studsNo
source_mesh_pathNo
execute_in_studioNo
expected_place_idNo
expected_rig_heightNo
foregrip_offset_posNo
attach_primary_in_ikNo
expected_session_nonceNo
replace_existing_weldsNo
foregrip_offset_rot_degNo
invoke_upstream_studiomcp_if_plugin_offlineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.