blender_material_list
Lists every material in the current file, giving you a clear inventory to manage assets or plan modeling steps.
Instructions
List all materials in the file
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Lists every material in the current file, giving you a clear inventory to manage assets or plan modeling steps.
List all materials in the file
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Does not mention that it is a read-only operation, nor does it specify the output format or behavior when no materials exist. Since there are no annotations, the description fails to provide necessary behavioral details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no unnecessary words. It is concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
As a simple tool, it lacks clarification on what the returned list contains (e.g., names, objects) and whether it includes empty results. Without an output schema, this ambiguity is not resolved.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, so the schema covers all (vacuously). The description adds no parameter-specific meaning, and the baseline for high coverage is 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action (list) and the resource (materials in the file). It distinguishes from other material tools like create or assign, making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this tool versus alternatives, such as before modifying materials or checking existing ones. Lacks context or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SekaiNoOwari77/mcp-3d-modeling-agent'
If you have feedback or need assistance with the MCP directory API, please join our Discord server