Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

rename

Changes an existing object's name in the active Blender scene and verifies the update.

Instructions

Renames an existing object in the active scene with targeted verification.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCurrent object name.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
new_nameYesNew name for the object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. It confirms this is a mutation of an existing object, but says nothing about what "verification" entails, whether the rename can collide with an existing name, whether it is reversible, or how the untrusted `approved` flag interacts with it — all important for a rename operation.

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?

It is a single front-loaded sentence, which is efficient, but the trailing clause "with targeted verification" is vague filler that costs the reader attention without conveying actionable information.

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?

For a mutation tool with four parameters, no annotations, no output schema, and a security-sensitive `approved` flag explicitly marked untrusted, this description is too thin. It leaves the verification behavior and the approval semantics unexplained, so an agent lacks what it needs to invoke the tool confidently.

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

Parameters3/5

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

Schema description coverage is 100%, so `name`, `new_name`, `task_id`, and `approved` are already documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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

Purpose3/5

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

"Renames an existing object in the active scene" gives a clear verb+resource, but the definition does not distinguish this from the sibling `rename_object`, and the trailing phrase "with targeted verification" is unexplained. An agent cannot tell which of the two rename tools to pick from this text alone.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus `rename_object` or any other sibling, and no prerequisites or exclusions. The phrase "targeted verification" hints at an extra check but never says what triggers it or when it matters.

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