Skip to main content
Glama

assign_material

Apply a material to an object by targeting an existing slot or creating a new slot when none is specified.

Instructions

Assign a material to an object. If slot is specified, replaces that slot; otherwise appends a new slot.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotNo
objectYes
materialYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0+hardened.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the key side effect: replacing an existing slot when slot is specified, otherwise appending a new slot. This is meaningful beyond the name and schema, though it does not mention prerequisites or error behavior.

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?

Two concise sentences with the core action front-loaded and the conditional slot behavior immediately following. Every word earns its place.

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 is simple and has an output schema, so return details are not necessary. However, with no annotations and no usage guidance, the description leaves some gaps around prerequisites and material/object identifier semantics, making it adequate but not complete.

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 explains the optional slot parameter's effect well, but object and material are only glossed as 'an object' and 'a material' without specifying identifier formats or whether the material must already exist.

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: 'Assign a material to an object,' and adds precise slot behavior ('replaces that slot; otherwise appends a new slot'). This clearly distinguishes it from material creation, removal, or property-setting siblings.

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 guidance is given about when to use this tool versus alternatives such as set_material_property or create_material. The intended use is implied by the name and description, but no exclusions or alternative conditions are stated.

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