Skip to main content
Glama

ai_modeling_brush_parts

Read-only

Lists model part names and texture sizes to identify target parts for Magic Brush selection.

Instructions

list model part names and texture sizes for Magic Brush selection

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": {
      "model_path": "<model_path>"
    },
    "name": "ai_modeling_brush_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the result contains part names and texture sizes, which is useful, but says nothing about how the model is resolved, whether it must be loaded/open, or any failure modes for an open-world read.

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?

A single front-loaded sentence with no filler; the resource and its purpose come first and nothing is redundant.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does state what is returned (part names and texture sizes), which is the main thing an agent needs. The remaining gap is the unexplained model_path argument, which keeps it short of full completeness.

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?

There is a single required parameter, model_path, with 0% schema description coverage, and the description never explains its format, expected source, or constraints. With one undocumented parameter the description should compensate, and it does not.

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?

States a specific verb ("list") and concrete resources ("model part names and texture sizes") plus the context ("for Magic Brush selection"). It is distinguishable from siblings like ai_modeling_brush_paint or ai_modeling_brush_bake, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "for Magic Brush selection" implies the situation in which to call it, but there is no explicit when-to-use/when-not guidance and no mention of which sibling to prefer for related brush operations. Usage is inferable rather than 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