Skip to main content
Glama
sosadly
by sosadly

paint_texture

Paint directly on a texture with absolute pixel coordinates for precise control. Use shapes, lines, gradients, dither patterns, and noise to edit entire sheets.

Instructions

Paint directly on a texture with absolute pixel coordinates. Use this for whole-sheet work; for painting onto a specific cube face, paint_faces (face-relative coords) is usually easier. Ops run in order on the canvas (origin top-left, y down).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsYesDrawing operations. Each op has a `type` and (where relevant) a `color` (CSS color). Types: pixel{x,y}; rect{x,y,width,height,fill?,line_width?}; line{x1,y1,x2,y2,line_width?}; circle{x,y,radius,fill?,line_width?}; ellipse{x,y,width,height,fill?,line_width?}; polygon{points:[[x,y],...],fill?,line_width?}; gradient{x1,y1,x2,y2,x,y,width,height,stops:[[offset,color],...]}; dither{x,y,width,height,color,color2?,density?} (pixel pattern — stripes/bandages); noise{x,y,width,height,amount?,color?,mono?} (organic fur/skin texture); fill_all{}; clear{x?,y?,width?,height?}.
textureYesuuid or name of the texture to paint.
edit_nameNoUndo entry label.
Behavior4/5

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

The description discloses the coordinate system and execution order, which is helpful. However, without annotations, it does not explicitly state that the texture is modified in place or discuss undo behavior, though edit_name hints at it. Leaves a small gap in full transparency.

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?

The description is three sentences, each contributing essential information: purpose, usage guidance, and coordinate system. No redundancy or filler.

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?

Given the tool's complexity (multiple op types), the description covers the main aspects. However, it does not explicitly state the outcome (e.g., texture is updated) or mention error conditions. Minor lack of completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant value beyond the schema by listing all operation types and their parameters with examples. Schema coverage is 100%, but the description enriches understanding of the ops array structure.

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

Purpose5/5

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

The description clearly states the verb (paint), resource (texture), and coordinate system (absolute pixel coordinates). It also distinguishes from the sibling tool paint_faces by noting the coordinate difference.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool (whole-sheet work) and when to use the alternative (paint_faces for face-relative coordinates). It also mentions that ops run in order, providing clear context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sosadly/blockbench-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server