delete_objectsRemove Maya scene nodes by exact name or wildcard pattern, targeting a specific session when multiple instances are connected.
Delete nodes by name or wildcard pattern.
| Name | Required | Description | Default |
|---|---|---|---|
| patterns | Yes | Node names or wildcard patterns to delete. | |
| session_key | No | Target Maya session; omit if only one is connected. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It signals a destructive action via 'Delete' but omits critical details: irreversibility, confirmation requirements, session targeting implications, or side effects on related nodes.
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 description is a single, front-loaded sentence with no wasted words. It is appropriately sized for a terse statement, though its brevity contributes to gaps in other dimensions.
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?
For a destructive operation with no annotations and no usage guidance, the description is incomplete. Output schema exists and handles return values, but the description fails to address safety, reversibility, or session context that an agent needs before invoking a delete tool.
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 description coverage is 100%, so the baseline is 3. The description restates the pattern matching capability already documented in the schema and adds no new syntax, format, or edge-case guidance for either parameter.
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?
Description states a specific verb ('Delete') and resource ('nodes') with the matching mechanism ('by name or wildcard pattern'). It clearly conveys what the tool does, though it does not differentiate from siblings (none of which are deletion tools).
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 on when to use this tool versus alternatives, no prerequisites, and no conditions or exclusions. The description simply states the action without any contextual routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.