A
licenseB
qualityB
maintenanceEnables users to generate rigged, game-ready gun models in Blender from parameterized presets or platforms, including attachments, animation clips, fact sheets, and reference-photo validation.
10
41 PyPI
2
MIT
Coating Lab
by hpdkhoa
Related Servers
Alternatives to Coating Lab
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI clients to track first-person weapon bugs as measurable cases, run a game's own probe to gather metrics and screenshots, and compare candidate fixes against a baseline before a change is approved. It also reads posed weapon parts dumps, rebuilds animation clips in Blender, and validates probe contracts.672MIT
- AlicenseBqualityBmaintenanceEnables models to pose and measure first-person arms and a rifle in Blender, reporting positions in named frames, clearances, visibility, screen placement, and solving rifle moves against goals.1758 PyPI1MIT
- AlicenseAqualityCmaintenanceenables creation of Enfusion/Arma Reforger PBR materials — generates maps, packs Enfusion channels (BCR/NMO), writes .emat files, and stages them atomatically into addons via MCP or CLI.6GPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables conversational control of Adobe Substance 3D Painter for look-dev iteration, including baking, smart materials, and generator parameter tuning.MIT
- AlicenseCqualityBmaintenanceEnables AI agents to build game assets in Blender by modeling, lighting, rendering previews to inspect and correct, validating against engine budgets, and exporting to GLB/FBX.126MIT
TDQS
C2.8/5.0
Scored across 13 tools
Disambiguation4/5
Most tools are cleanly separated by resource+action: discovery (list_finishes, read_finish, list_wear_levels, list_templates), production (spec_for_modellab, engine_params, bake, render_variants), and validation. The risk cluster is the four validation tools (check_library, check_finish, check_coating, validate_spec), which all sound like 'check' but operate on different objects; the descriptions mostly disambiguate them, though an agent may still hesitate between check_finish and check_library.
Naming Consistency4/5
Most names follow verb_noun (read_finish, list_finishes, check_library, validate_spec, render_variants), which is predictable. A few deviate into noun-only forms (engine_params, bake, spec_for_modellab), a minor inconsistency but nothing confusing.
Tool Count5/5
13 tools sit comfortably in the healthy range for a domain with discovery, validation, spec-generation, baking, and rendering stages. Each tool appears to earn its place without redundancy.
Completeness4/5
The workflow is covered end-to-end: inspect existing finishes/templates/wear levels, describe an external model, generate a spec, validate it, bake masks, and render look-dev sheets. The one gap is library mutation — check_finish validates 'a finish of your own... before you add it' but there is no add/update_finish tool, so that path dead-ends at manual editing.
Maintenance
ActivityMaintained
ResponsivenessSyncing