Skip to main content
Glama

create_transparent_material

Generate a transparent Blender material with adjustable alpha and color for windows, glass, or translucent surfaces.

Instructions

Create a transparent material.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_transparent_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
alphaNo
colorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only restates the name. It does not say whether the material is attached to an object, added to a slot, whether it mutates scene state, what permissions are needed, or how alpha blending is handled. The mutation is implied but not disclosed.

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 sentence is concise and front-loaded with no wasted wording, but it is under-specified rather than efficiently terse. There is no structure to help an agent parse behavior or parameters.

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 the tool has three undocumented parameters and no annotations. For a material-creation mutation, the definition is too thin to tell an agent how the call behaves or how to populate the inputs correctly.

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

Parameters2/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 for three undocumented parameters, and it adds nothing. It does not explain the accepted range or meaning of alpha, the format of the color array (RGB vs RGBA, normalized vs 0-255), or what name controls.

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?

The description gives a specific verb and resource ('Create a transparent material'), so the agent knows the operation and target. It stops short of distinguishing this from nearby siblings like create_glass_material or create_material, and 'transparent' is ambiguous against glass, but the core purpose is clear.

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 choose this tool over create_glass_material, create_material, or the other material creators. No prerequisites, no exclusions, and no context about the creating workflow are provided.

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