Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

list_materials

Lists materials in a Blender file with node usage, user counts, base diffuse color, metallic/roughness values, and linked image texture filenames for inspection.

Instructions

List materials defined in the Blender file, including node usage, user counts, base diffuse color, metallic/roughness values, and linked image texture file names.

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": "list_materials"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of materials to return.
offsetNoPagination offset.
filter_nameNoOptional substring filter to match material names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the salient output attributes (node usage, user counts, base diffuse color, metallic/roughness, image texture file names). However it never confirms this is a non-mutating read, says nothing about pagination behavior despite limit/offset parameters, or about cost/scale on large files.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; every listed attribute is meaningful given there is no output schema. The return-value enumeration is slightly dense as a trailing clause, which keeps it from a 5.

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?

Because no output schema exists, the description correctly spends its length describing return contents, and the three parameters are schema-documented. Still, for a tool with zero annotations it omits the safety profile (read-only confirmation) and pagination result behavior, leaving gaps an agent would want closed.

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 100%, so limit, offset, and filter_name are already fully documented in structured form, establishing the baseline of 3. The description adds no extra meaning about filtering semantics or ordering of results beyond what the schema states.

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?

Names a specific verb and resource ("List materials defined in the Blender file") and even enumerates the returned attributes, so the agent knows exactly what it gets. It never distinguishes itself from nearby siblings such as assign_material or bake_materials, so it stops short of a 5.

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 explicit statement of when to call this versus alternatives, no prerequisites, and no exclusions. Usage is only implied by the read-style verb "List", leaving the agent to infer the inventory/diagnostic use case.

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