Skip to main content
Glama

create_metallic_material

Creates a metallic material in Blender with configurable name, color, and roughness so you can apply metal shading to 3D models.

Instructions

Create a metallic 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_metallic_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
roughnessNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/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 disclosure burden, yet it says nothing about whether the material is auto-assigned to an object, whether it is saved to the blend file, what happens with default values, or whether the operation is reversible. Only the bare mutation intent ('create') is conveyed.

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

Conciseness2/5

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

The single sentence is efficient on its face but is under-specified rather than concise; it contains no information beyond the tool name, so there is nothing to front-load or structure.

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

Completeness1/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 explained, but for a three-parameter creation tool with zero annotations and zero schema descriptions, the definition leaves the agent without any information needed to call it correctly or distinguish it from sibling creators.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, and the description does not name or explain any of them. It omits that name and color are nullable and that roughness defaults to 0.2, so the schema's own defaults are the only guidance the agent gets.

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

Purpose2/5

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

"Create a metallic material" restates the tool name verbatim and adds no scope, output, or distinguishing detail. An agent learns only that a metallic material is produced, with no hint of how this differs from create_material or create_glass_material.

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 exclusions, and no mention of the sibling material-creation tools (glass, emission, transparent) or of create_material as a general alternative. The agent must infer selection purely 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