blender-mcp

by kleer001

Overview Schema Source Related Servers Discussions Admin

Python

Local

rename_object

Rename a Blender object and get the actual assigned name, even if automatic numbering appends a suffix.

Instructions

Rename an object. Returns the actual name assigned (may be auto-incremented).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "new_name": "<new_name>"
    },
    "name": "rename_object"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`new_name`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It proactively reveals a key behavior: the actual name assigned may be auto-incremented, which is critical for users to understand. This goes beyond simple 'rename' semantics, though it does not cover error cases or edge conditions like invalid names or non-existent objects.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that delivers the core purpose and a key behavioral nuance with zero waste. It is appropriately concise for a simple tool.

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

Completeness4/5

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

Given the tool's simplicity (2 parameters, no nested objects), the description is mostly complete. It mentions the return value and auto-increment behavior, and the output schema provides additional structure. However, it omits potential error scenarios or prerequisites, which would be useful for a fully complete picture.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate by explaining the parameters. It does not explicitly define 'name' as the current name or 'new_name' as the desired name beyond what the parameter names imply. The description adds no semantic value to the schema, making the meaning ambiguous for new users.

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

Purpose5/5

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

The description clearly states the action ('Rename') and the resource ('object'), with a specific verb and object. It also mentions the return behavior, distinguishing it as a rename operation rather than create/delete. No sibling tool covers renaming, so it stands out clearly.

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

Usage Guidelines3/5

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

The description implies that this tool is used to rename objects, but it provides no explicit guidance on when to use it versus alternatives like duplicate_object or set_transform, nor any preconditions such as the object needing to exist. It offers clear context but no exclusions or alternatives.

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

Deploy Server