Skip to main content
Glama
HoldMyBeer-gg

blend-ai

by HoldMyBeer-gg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mark_sharp

Mark or clear sharp edges on a Blender mesh to control auto-smooth shading, creating hard edges where needed. Works on the whole mesh or the current selection.

Instructions

Mark or clear sharp edges on a mesh.

Sharp edges control auto-smooth shading. Edges marked as sharp will have a hard edge in the shading even with smooth shading enabled.

Args: object_name: Name of the mesh object. clear: If True, clear sharp marks instead of setting them.

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
clearNo
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. Addedv1.2.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a decent job: it discloses what the operation changes in shading terms, that `clear` inverts the effect rather than performing a different action, and that a confirmation dict is returned. It omits anything about reversibility/undo or required edit-mode state, which for a mutation tool keeps it below 5.

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?

Front-loaded with the core purpose in the first line, then a useful one-sentence rationale, then clearly separated Args and Returns blocks. Efficient overall; only the shading explanation is slightly padded relative to need.

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 return values need not be detailed, and the brief 'confirmation dict' note is sufficient. All parameters, defaults, and the selection prerequisite are covered; the only gap is edit-mode/permission prerequisites for a mesh-mutating tool.

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 description coverage is 0%, so the description must compensate, and it does: all three parameters are explained, including the boolean inversion semantics of `clear` and the enum meaning plus default of `selection`. Nothing transforms or formats beyond that, so a 4 rather than a 5.

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 pair plus resource ('Mark or clear sharp edges on a mesh') and explains what sharp edges materially do ('hard edge in the shading even with smooth shading enabled'), which is genuinely informative. It does not explicitly differentiate from nearby siblings such as set_edge_crease or mark_seam, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives real operating context: the 'ALL' vs 'CURRENT' selection mode determines whether the whole mesh or only the current selection is affected, and it tells the agent to run the select_* tools first. It offers no when-not-to-use guidance or routing against alternatives like set_edge_crease, so no 5.

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