Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_curve_property

Adjust a Blender curve object's bevel depth, extrusion, fill mode, or resolution to control its shape, thickness, and render output.

Instructions

Set a property on a curve object.

Args: curve_name: Name of the curve object. property: Property to set - resolution_u, fill_mode, bevel_depth, bevel_resolution, extrude, twist_mode, or use_fill_caps. value: Value to set. Type depends on property.

Returns: Confirmation dict with property name and new value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
propertyYes
curve_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 / property / enum
      Added value: +[
+  "bevel_depth",
+  "bevel_resolution",
+  "extrude",
+  "fill_mode",
+  "resolution_u",
+  "twist_mode",
+  "use_fill_caps"
+]
  2. First observedv0.1.0

TDQS

B3.3/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 of behavioral disclosure. It mentions a confirmation return, but does not state side effects, permissions, error conditions, whether the curve must exist, or whether changes are reversible. For a mutation tool, this leaves important behavioral context unstated.

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

Conciseness5/5

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

The description is well structured and front-loaded: the core action appears first, followed by Args and Returns. Every line is useful, and there is no redundant or vague filler.

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?

The tool has an output schema, so return values are already covered, and the description lists all parameter names and the property enum. However, with no annotations and zero schema description coverage, the description should do more to clarify value types, prerequisites, and mutation behavior. It is adequate but incomplete for a property-setting operation.

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 0%, so the description must compensate. It names all three parameters and lists the allowed property values, which is valuable. However, it only says the value type depends on the property and never maps specific properties to expected types or ranges, leaving a significant semantic gap.

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

Purpose5/5

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

The description states a specific verb and resource: 'Set a property on a curve object.' It names the exact curve properties that can be set, which clearly distinguishes this tool from generic property setters like set_modifier_property or set_object_visibility. An agent can identify the tool's purpose without opening the schema.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as set_modifier_property or other curve-editing tools. It does not mention prerequisites, modes, or exclusions. Usage is only implied by the tool name and stated purpose.

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