Skip to main content
Glama

ai_modeling_brush_pick

Read-only

Pick original texture color at a UV coordinate or nearest 3D surface without lighting, and use a brush preview to sample edited colors.

Instructions

pick the original texture color at a UV coordinate or nearest 3D surface, without lighting; use a brush preview to pick edited colors

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_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
uvNo
rayNo
part_nameNo
model_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description usefully adds that the sample is unlit ('without lighting'), which explains the returned color semantics, but says nothing about return format, what happens if both uv and ray are supplied, or failure modes for an openWorld tool.

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 compact sentence with the core capability front-loaded and the alternative path trailing. Dense but no filler; a semicolon split for the two clauses would aid scanning slightly.

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?

For a 4-parameter tool with a nested ray object, 0% schema coverage, and no output schema, the description leaves too much unexplained: model_path and part_name meanings, precedence between uv and ray, and the shape of the returned color are all absent.

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 description coverage is 0% for 4 parameters, so the description must carry the load. It only implicitly covers 'uv' and 'ray' (via 'UV coordinate or nearest 3D surface'); 'model_path' and 'part_name' are never mentioned, and the required-vs-optional relationship is unstated.

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 ('pick') and resource ('original texture color') along with the two sampling modes (UV coordinate or nearest 3D surface). This distinguishes it from ai_modeling_brush_paint, though it doesn't name siblings 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 clause 'use a brush preview to pick edited colors' implies the alternative path when edited rather than original colors are wanted, but it is phrased obliquely and gives no explicit when-not guidance or prerequisites.

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