Voidless

make_normal_map

Make a normal map for an image asset, for 2D lights in a game engine: which way each pixel faces, so a moving light shades it. The shape comes from a depth model, the drawn detail from the picture. PNG at the picture's own size, OpenGL style (green = up: Godot and Unity read it as is; flip green for Unreal). Pass frameId (from get_asset) for an edit, or an animation (one map per frame); leave it out for the image itself. Free.

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": {
      "id": "<id>"
    },
    "name": "make_normal_map"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset ID (from list_assets / get_asset or a previous result)
`frameId`	No	Optional: the frame (an edit or an animation, from get_asset) to make it for. Empty = the image itself.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the mutation/idempotency profile; the description adds substantial context beyond them: output is PNG at the source image's own size, OpenGL green-up convention with engine-specific notes (Godot/Unity read as-is, flip for Unreal), and that the operation is free. That is exactly the kind of behavioral detail annotations cannot carry.

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?

Front-loaded with the purpose, then output format, then parameter routing. Dense and mostly waste-free, though the engine-convention parenthetical and the trailing 'Free.' make it slightly run-on.

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

Completeness5/5

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

No output schema exists, yet the description covers the return artifact (PNG, native size, channel convention) and both parameters' behavior. For a two-parameter generation tool, nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: frameId comes from get_asset, an animation yields one map per frame, and omitting it targets the image itself. It does not clarify the id parameter's provenance beyond what the schema already says.

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?

States a specific verb and resource ('Make a normal map for an image asset') and immediately explains the concept in functional terms ('which way each pixel faces, so a moving light shades it'). It also distinguishes the source of the data (depth model for shape, picture for detail), which no sibling tool does.

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

Usage Guidelines4/5

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

Gives explicit conditional guidance: pass frameId for an edit or an animation, leave it out for the image itself. It does not name an alternative sibling (e.g. make_glow_map) or state when not to use it, so it falls short of full routing guidance.

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

All Voidless tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?