Voidless

flip_left_side

Mirror every right, up-right and down-right animation on an asset that has no left twin into one (walk-right -> walk-left). The 8-way turns draw the left side as a mirror of the right, so animate the right-facing turns and flip for the rest. Free (no model call). One-sided details swap sides.

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": "flip_left_side"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Asset ID (from list_assets / get_asset or a previous result)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Adds genuinely useful context beyond annotations: cost ('Free, no model call') and the side-swap semantics for one-sided details. Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation, and the description does not describe what is overwritten or what the response contains when a twin already exists.

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 transformation rule and a concrete example, but the middle sentence ('The 8-way turns draw the left side as a mirror of the right...') largely restates the opening sentence, adding a bit of redundancy.

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?

A mutation tool with one required, well-documented parameter and no output schema; the description covers cost, directional scope, and the twin prerequisite. Missing only return/error behavior for the edge case where a left counterpart partially exists.

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?

The single `id` parameter is fully described in the schema (100% coverage), so the schema carries the load. The description adds no extra meaning about the id beyond pointing at the asset concept implicitly.

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 (mirror/flip) and a precise resource (right, up-right, down-right animations on an asset lacking a left twin), with a concrete example (walk-right -> walk-left). This is clearly distinguishable from siblings like rotate_sprite or generate_animation_set.

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 clear workflow directive: animate the right-facing turns first and then use this tool for the rest, plus a constraint that the asset must have no left twin. It stops short of naming the alternative tool to animate with or stating what happens if a left-side animation already exists.

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?