Skip to main content
Glama

get_material_info

Inspect a named Blender material and its nodes to understand shader structure, verify properties, and guide edits or debugging.

Instructions

Inspect a material and its nodes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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, and it only implies a read via 'Inspect'. It does not state what happens if the material name is unknown, whether it traverses node graphs recursively, or anything about cost or side effects. The existence of an output schema offsets the need to describe return values, but the operational behavior is essentially undisclosed.

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?

One short sentence with no wasted words, but the brevity comes at the cost of under-specification rather than efficiency. There is nothing front-loaded beyond the bare verb and resource.

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?

Although the tool is simple (one required string) and has an output schema, the absence of annotations and any parameter meaning leaves the agent without enough to call it confidently or distinguish it from get_material_nodes. A single clarifying clause about what 'name' refers to and how nodes are handled would close most of the gap.

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 coverage is 0%, so the single 'name' parameter is undocumented in both schema and description. The description does not say whether 'name' is a material name, a node name, or a path, nor whether it must match exactly or can be a partial identifier.

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

Purpose3/5

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

The description names a verb ('Inspect') and a resource ('material'), so the general intent is readable. However, 'and its nodes' is ambiguous: the sibling get_material_nodes appears to cover node-level data, and the description never clarifies whether this tool duplicates that, embeds it, or returns only summary material properties.

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 when-to-use guidance, no mention of alternatives such as get_material_nodes or get_materials, and no stated prerequisites. The agent must guess whether this is the right entry point for material inspection versus the more specific siblings.

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