Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_location

Position a Blender object by specifying its name and a three-number XYZ coordinate list; returns the object name and updated location.

Instructions

Set the position of an object.

Args: object_name: Name of the object. location: XYZ position as a 3-element list/tuple.

Returns: Dict with the object name and new location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYes
object_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.0
    • addedInput schema / properties / location / maxItems
      Added value: +3
    • addedInput schema / properties / location / minItems
      Added value: +3
    • removedInput schema / properties / name
      Removed value: -{
-  "title": "Name",
-  "type": "string"
-}
    • addedInput schema / properties / object_name
      Added value: +{
+  "title": "Object Name",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "location"
-]New value: +[
+  "object_name",
+  "location"
+]
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation but never states the coordinate space (local vs world), the units, or whether it overwrites existing position. It does at least disclose the return shape (object name and new location).

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?

Short, front-loaded, and the Args/Returns structure is easy to scan. Every line earns its place, though the numbered parameters are fairly minimal.

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

Completeness3/5

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

Output schema exists so return values needn't be explained. For a mutation tool with zero annotation coverage and zero schema descriptions, the description covers the argument meanings but omits the behavioral facts an agent needs (units, coordinate space, permission assumptions).

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 coverage is 0%, so the description must compensate; it adds meaningful semantics by explaining that location is an "XYZ position as a 3-element list/tuple," which the schema only conveys via minItems/maxItems=3. However, it omits units and coordinate space, leaving the most consequential ambiguity unaddressed.

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?

Clear verb+resource: "Set the position of an object." The word "position" distinguishes it from siblings like set_rotation and set_scale, so an agent can infer the axis of manipulation. It stops short of explicitly naming those siblings as alternatives.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives (set_rotation, set_scale, apply_transforms, set_origin). The agent must infer usage entirely.

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