Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

loop_cut

Adds a set number of loop cuts to a Blender mesh object, applying them to the whole mesh or the current selection to create new edges for modeling.

Instructions

Add loop cuts to a mesh object.

Args: object_name: Name of the mesh object. cuts: Number of loop cuts. Range: 1-100.

selection: "ALL" to act on the whole mesh, or "CURRENT" to act only
    on what is already selected. Use the select_* tools to choose
    first. Defaults to "ALL".

Returns: Confirmation dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cutsNo
selectionNoALL
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / selection
      Added value: +{
+  "default": "ALL",
+  "enum": [
+    "ALL",
+    "CURRENT"
+  ],
+  "title": "Selection",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral trait — selection="ALL" acts on the whole mesh while "CURRENT" restricts to the existing selection, establishing a prerequisite (select first). It omits mutating-operation concerns such as edit-mode requirements, reversibility/undo, or permission needs.

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

Conciseness4/5

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

Purpose is front-loaded in the first line, with Args and Returns cleanly separated and no filler. The Args block is more verbose than strictly needed but each line carries usable information.

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?

An output schema exists, so the terse "Returns: Confirmation dict" is sufficient. Parameter and selection behavior are covered; only edit-mode/undo context for a geometry-mutating tool is missing, a minor gap.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate and largely does: it documents all three parameters, adds the cuts range 1-100 absent from the schema, and defines the ALL/CURRENT enum semantics plus the pre-selection dependency. object_name is only restated, but overall it adds substantial meaning beyond the bare schema.

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?

States a specific verb and resource ("Add loop cuts to a mesh object"), making the operation legible against mesh-edit siblings. It does not, however, differentiate itself from close alternatives like subdivide_mesh, bevel_edges, or bridge_edge_loops, so an agent must infer the distinction from the name alone.

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 selection parameter text gives real routing guidance ("Use the select_* tools to choose first"), which tells the agent how to set up a pre-selection. There is no explicit when-to-use-this-vs-subdivide_mesh guidance, so usage is only implied.

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