Skip to main content
Glama

rename_collection

Renames a Blender collection by specifying its current name and a new name, helping organize scene data and keep collection labels accurate.

Instructions

Rename a collection.

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

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

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden for a mutation tool, and it discloses nothing. It does not say whether renaming fails on duplicate names, whether it is case-sensitive, whether contained objects are affected, or whether the operation is reversible.

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?

Four words contain no padding or wasted structure, and the single fact present is front-loaded. However, the terse sizing is a symptom of under-specification rather than disciplined editing, so it cannot score highly.

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, but everything else is missing for a mutating tool: no annotations, 0% parameter coverage, and no failure or side-effect information. For a two-parameter rename operation the gaps are still material.

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 would need to compensate, and it does not. The parameter names 'name' and 'new_name' with titles 'Name'/'New Name' are suggestive but the description never confirms that 'name' means the existing collection identifier and 'new_name' the replacement.

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

Purpose2/5

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

The description is a verbatim restatement of the tool name 'rename_collection' with only capitalization changed. It conveys no scope, no target domain (which kind of collection), and does nothing to distinguish it from sibling tools like rename_object or move_object_to_collection.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as rename_object for renaming a different resource type. The agent must infer applicability purely from the name.

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