Spine Render

Each tool targets a distinct action: parsing/inspection (spine_describe), GIF animation rendering (spine_render_animate), single-frame PNG rendering (spine_render_frame), and pricing lookup (spine_render_pricing). The two render tools are clearly separated by output type (animated GIF vs. single transparent PNG), so an agent can select confidently. No tool appears to duplicate another.

All tools share a consistent 'spine_' prefix and use snake_case, with the three action tools following a spine_render_<target> pattern. spine_describe is a minor deviation in that it omits the 'render_' infix, but it is still readable and predictable.

Four tools is lean but appropriate for a focused rendering service with a narrow domain (parse, render frame, render animation, check pricing). Nothing feels redundant, though the surface is on the thin side and could feel limited if users need batch or configuration operations.

The core lifecycle is covered: inspect a skeleton (spine_describe) before rendering it as a static frame or animation, plus a pricing/limits lookup to avoid surprise charges. Gaps are minor—no batch rendering, custom resolution/scale options, or sprite-sheet/multi-frame export—but agents can work around these using the existing frame and animation tools.