Skip to main content
Glama

set_object_shading

Set an object to smooth or flat shading in Blender to control how its surfaces react to light.

Instructions

Set smooth or flat shading.

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>"
    },
    "name": "set_object_shading"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
smoothNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/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, yet it says nothing about whether shading changes are reversible, whether they override custom normals or auto-smooth settings, whether the object must be a mesh, or what happens if the name is not found. For a mutation tool with zero structured behavioral coverage this is a notable gap.

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?

The single clause is efficient and front-loaded with no filler, but its brevity stems from under-specification rather than disciplined editing; a few more words could have carried the missing target and behavior.

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 described, but with no annotations and no schema descriptions the definition should still cover what 'name' refers to and the effect of the smooth flag. It does not, so an agent lacks enough to invoke this confidently.

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 for both parameters. It does clarify that the boolean toggles between smooth and flat (i.e. smooth=true), but leaves 'name' unexplained and does not mention the default of true.

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

Purpose3/5

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

"Set smooth or flat shading" gives a concrete verb and the two shading states, so the action is identifiable. However, it never says what is being shaded (an object identified by 'name') nor how it differs from sibling tools such as set_material_properties, leaving the target ambiguous.

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 guidance on when to use this versus material or modifier tools, and no preconditions (active object, object mode, existing mesh) are stated. The agent must infer context entirely from the tool 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