mesh.delete
Delete selected mesh elements including vertices, edges, or faces to refine geometry for game-ready assets.
Instructions
Delete selected mesh elements
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | VERT | |
| object | No |
Delete selected mesh elements including vertices, edges, or faces to refine geometry for game-ready assets.
Delete selected mesh elements
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | VERT | |
| object | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavior like destructiveness or mode requirements, but it only states the basic action, missing important context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is concise but lacks structure and fails to include necessary details, making it borderline under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the two parameters and no output schema, the description is incomplete—missing details on selection, mode, and parameter roles.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the description does not explain the 'type' enum or 'object' parameter, forcing reliance on schema without additional insight.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Delete' and resource 'mesh elements', distinguishing it from other mesh operations like extrude or bevel.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like dissolve or remove, nor any prerequisites like edit mode.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/OhaoTech/niua-blender-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server