Skip to main content
Glama
Sign In

Voidless

by dev.voidless
OverviewDiscussionsAdmin

add_to_asset_set

Add items to an existing asset set (from generate_asset_set), reusing everything it was made with: its view, style preset, style words, palette and style sheet. Or redraw_failed: true draws again, on a small sheet in the same style, just the pieces that failed their view check or were not cut out. Same price: 20 a sheet + 10 a cut; estimate_only shows it first. New pieces get world_height in the same reference character's heights (give size for each new item whose size matters: a new sheet has no reference character on it to measure against).

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": {
      "set_id": "<set_id>"
    },
    "name": "add_to_asset_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoNew items for the set
set_idYesThe set's id (generate_asset_set's set_id: its first sheet's asset id)
estimate_onlyNotrue = only the plan and the price; nothing is drawn or charged
redraw_failedNoAlso redraw the set's pieces that failed the view check or went missing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation. The description goes further with pricing ('20 a sheet + 10 a cut') and that estimate_only prices without charging or drawing, which the annotations do not say. It still omits whether the call is long-running, what a repeat call costs, and what the response contains for a paid mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information-dense with no filler, and the primary action is front-loaded. However it is delivered as one long run-on sentence that fuses three distinct concerns (inheritance, redraw mode, pricing/sizing) without structure, which slows an agent parsing the modes apart.

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?

For a four-parameter mutation with no output schema, it covers the essentials: what is inherited, the cost and preview option, the redraw branch, and the sizing caveat for new pieces. Remaining gaps (limits on item count, latency, return shape) are secondary and partly covered by the schema's maxItems.

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

Parameters3/5

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

Schema coverage is 100%, so all four parameters are documented in place. The description adds rationale for one of them – why `size` matters on a new sheet that has no reference character to measure against – but says nothing beyond the schema about items, set_id, redraw_failed or estimate_only. That marginal gain over a fully documented schema fits a 3.

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?

Names a specific verb and resource ('Add items to an existing asset set') and ties it back to the sibling that creates sets ('from generate_asset_set'), plus covers the secondary redraw_failed mode. An agent can distinguish this from generate_asset_set or generate_items without consulting the schema.

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?

Establishes the condition for use – extending a set that already exists, inheriting its view, style preset, style words, palette and style sheet – and explains the two optional modes (redraw_failed, estimate_only). It stops short of explicitly saying 'use generate_asset_set instead when you have no set yet', but the parenthetical implies it.

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

All Voidless toolsInspect
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