Voidless

tag_frame

DestructiveIdempotent

Add, remove or replace the tags on one frame of an image asset (an animation, edit or part), e.g. to mark which clip is 'idle' or 'final'. 8-way rotation frames cannot be tagged: their tags are the facings the animation presets rely on. 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>",
      "frameIndex": "<frameIndex>",
      "tags": "<tags>"
    },
    "name": "tag_frame"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset ID (from list_assets / get_asset or a previous result)
`mode`	No	add = keep existing tags and add these, remove = drop these, replace = set exactly these	add
`tags`	Yes	Tags, e.g. ['player', 'level-1']. Case-insensitive duplicates are merged
`frameIndex`	Yes	Frame id from get_asset

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral facts beyond them: a hard failure case (8-way rotation frames are untaggable and why), and that the operation is free, which matters for an agent managing credit spend. It stops short of saying what 'replace' discards, though the schema covers that.

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?

Two tight sentences plus a one-word cost note; the action and scope are front-loaded and the constraint follows. The trailing 'Free.' fragment is slightly abrupt but carries real decision-relevant information rather than filler.

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?

For a 4-parameter mutation with full schema coverage, no output schema, and annotations covering destructiveness and idempotency, the description supplies everything else an agent needs: scope, a usage example, a blocking edge case, and cost. Nothing material is missing.

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%, with descriptions already spelling out each mode ('add = keep existing, remove = drop these, replace = set exactly these'), the frame id source, and case-insensitive duplicate merging. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 three concrete verbs (add, remove, replace) against a precisely scoped resource: the tags on ONE FRAME of an image asset, with a parenthetical clarifying that an asset may be an animation, edit or part. That frame-level scoping implicitly separates it from the sibling tag_asset, but the sibling is never named, so the differentiation is left for the agent to infer.

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 a concrete use case ('mark which clip is idle or final') and an explicit exclusion: 8-way rotation frames cannot be tagged because their tags encode facings the animation presets depend on. It does not point to tag_asset as the alternative for whole-asset tagging, which keeps it short of a full when/when-not/alternative treatment.

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?