aegisub-mcp

Overview Schema Source Related Servers Discussions Admin

ass_svg_to_drawing

Convert SVG path data or SVG files into ASS drawing text for Aegisub subtitles, with scaling, rounding, and viewBox offset control.

Instructions

Convert SVG path data (or a whole .svg file) into ASS drawing text.

Either d (one or more d attributes, space separated) or svg_path (the file is read, its viewBox becomes the origin shift and every <path d="..."> is converted). view_box given as "x y w h" or [x, y, w, h] shifts the paths so the box origin becomes (0, 0).

scale multiplies every coordinate; round_to is the number of decimal places kept when serialising (0 = integer coordinates).

SVG and ASS both grow y downwards, so nothing is flipped. Supported commands: M L H V C S Q T A Z (relative forms too); quadratics are promoted to cubics and arcs to cubic segments.

Returns {drawing, bbox, size, center, path_count, view_box, scale, round_to, source}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`d`	No
`scale`	No
`round_to`	No
`svg_path`	No
`view_box`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly: it discloses the coordinate system behavior (SVG and ASS both grow y downwards, nothing flipped), supported SVG commands, conversion details (quadratics promoted to cubics, arcs to cubic segments), and the return object's keys.

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

Conciseness5/5

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

The description is front-loaded with the core purpose and then provides necessary technical detail in a well-structured, backtick-formatted way. Every sentence adds relevant information for this conversion task.

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?

Given zero schema description coverage, no annotations, five parameters, and a non-trivial conversion domain, the description is complete enough for an agent to invoke correctly. It even repeats the return keys, though an output schema exists, so nothing critical is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate and does: it defines d, svg_path, view_box (including string and array formats), scale, and round_to with enough precision to use each parameter correctly.

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?

States a specific verb and resource: convert SVG path data or .svg files into ASS drawing text. This clearly distinguishes it from sibling tools like ass_drawing_to_svg, which performs the reverse conversion.

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?

Explains the two input modes (d vs svg_path) and the effects of view_box, scale, and round_to, giving clear context for how to invoke the tool. However, it does not explicitly name when to use this tool versus its reverse sibling ass_drawing_to_svg, so alternatives are not directly addressed.

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

Deploy Server