3D-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 125 tools
The tools are generally well-differentiated by resource type (e.g., BlendShapes, Materials) and action (create, delete, update), but there is some overlap in batch operations like batchSetProperty and individual update tools, which could cause confusion. However, descriptions help clarify the scope, preventing severe misselection.
Most tools follow a consistent verb_noun pattern (e.g., createBlendShapes, deleteMaterials, updateVertexs), with clear conventions for CRUD operations. Minor inconsistencies include 'getQuadView' (not pluralized) and 'performGroupOperations' (less specific), but overall naming is predictable and readable.
With 125 tools, the count is excessive for a typical MCP server, making it overwhelming and difficult to navigate. While it covers a broad 3D modeling domain, many tools could be consolidated or omitted without losing functionality, indicating poor scoping.
The tool set provides comprehensive coverage for 3D modeling, including full CRUD operations for various resources (e.g., meshes, materials, UV maps), transformation tools, import/export, and utility functions like undo/redo. No obvious gaps exist for the domain, ensuring agents can handle complex workflows.