Voidless

make_glow_map

Make a glow map from an edit that switched lights on (or made a night version with lights glowing): the light the edit added over the picture it came from, on transparency, for an additive or emissive layer in a game. Same size as the picture. Pass the edit's frameId (from get_asset). 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>",
      "frameId": "<frameId>"
    },
    "name": "make_glow_map"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset ID (from list_assets / get_asset or a previous result)
`frameId`	Yes	The edit (a frame from get_asset) whose light to keep

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare it is not read-only, not idempotent, not destructive and closed-world. The description adds real context beyond that: output is same size as the source picture, delivered on transparency, and the operation is free. It does not say whether a new asset is created or where the result lands.

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?

The core purpose and the frameId source are front-loaded in the first clause, and no sentence is filler. The parenthetical and the trailing fragments ("Same size as the picture. Free.") read as run-on notes rather than a clean structure.

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 carries the burden of describing the return value, and it does: a transparency layer the same size as the source picture. The only gap is what happens to the produced map (new asset vs. attached to the frame), which an agent might still need.

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 schema already documents both id and frameId. The description still adds meaning by constraining frameId to an edit that switched lights on, which is a semantic filter the schema's "the edit whose light to keep" only hints at.

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 names a specific verb+resource ("Make a glow map") and then defines the artifact precisely: the light an edit added over its source picture, on transparency, usable as an additive/emissive layer. That definition alone separates it from siblings like make_normal_map or edit_image without any schema reading.

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?

It states the triggering condition clearly: use it on an edit that switched lights on or produced a night version with glowing lights, and it points at get_asset as the source of frameId. It stops short of naming an alternative tool or a when-not case (e.g. edits that didn't add light).

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?