Skip to main content
Glama

rename_object

Change a Blender object’s name by specifying its current name and the new name to keep scenes organized and identifiable.

Instructions

Rename an object.

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

NameRequiredDescriptionDefault
nameYes
new_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it adds nothing: it does not say whether the object must already exist, what happens on a duplicate name, whether this renames data-blocks or only scene objects, or whether it targets the currently active object.

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

Conciseness3/5

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

One short sentence with zero wasted words, but the brevity comes from under-specification rather than disciplined editing. There is no front-loaded context beyond the bare verb and object.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for a mutation tool with no annotations and undocumented parameters, the description provides nowhere near enough context for an agent to invoke it confidently.

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% — the schema exposes only titles 'Name' and 'New Name' with no descriptions. The description does not compensate at all, leaving it unclear whether 'name' is an identifier, an internal ID, or the current display name.

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

Purpose4/5

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

"Rename an object" states a specific verb and resource, so the agent knows precisely what operation is performed. It loses the top mark only because it does not distinguish the tool from its sibling rename_collection or clarify what counts as an 'object'.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no reference to any alternative such as rename_collection or modify_object. The agent is left to infer entirely when this tool applies.

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

Deploy Server

Other Tools