Skip to main content
Glama

AMNT SVG

by io.amnt
OverviewDiscussionsAdmin

Server Details

Text or image to clean, editable SVG from $0.01. Free SVG library + agent search, no key.

Ownership verified
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: agents_search finds marketplace agents, svg_generate creates new SVGs from text, svg_vectorize converts existing images, and svg_library_search/get handle library discovery and retrieval. The split between generation and vectorization is explicitly clarified in the descriptions, leaving no meaningful overlap.

Naming Consistency5/5

All tool names follow a consistent snake_case resource_action pattern: agents_search, svg_generate, svg_library_get, svg_library_search, and svg_vectorize. The resource prefix (agents vs svg vs svg_library) varies logically by domain, but the action-last convention is uniform.

Tool Count5/5

Five tools is well-scoped for an SVG generation, vectorization, and library service. Each tool earns its place, and the addition of agents_search is a compact discovery aid rather than bloat.

Completeness4/5

The core SVG workflows are covered: generate from text, vectorize an existing image, and search/get library items. Minor gaps exist, such as no direct tool for editing or post-processing an existing SVG or for running a discovered agent, but agents can work around these limitations.

Available Tools

5 tools
svg_generateAInspect

AMNT SVG: describe a picture and get a clean, editable SVG (real shapes, not a bitmap). Pick a "model": amnt-auto (AMNT Auto) picks the best one per request ($0.01-$0.25, shown before it runs); without one it uses AMNT Draw 1.2: $0.05 standard, $0.15 HD, any shape. Takes 8-60 s.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNocutout = no overlapping shapes, for Figma and cutting machines.
modelNoThe AMNT model. Leave it out for AMNT Draw 1.2, the default. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into a clean SVG. Logos and icons come back as tiny clean code. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG. Every moving part is its own named group. Hand-drawn or flat.
styleNoflat, icon and logo trace cleanest.
aspectNo"auto", 1:1, 4:5, 3:4, 2:3, 9:16, 1:2, 5:4, 4:3, 3:2, 16:9, 2:1, or any W:H up to 3:1. Same price in every shape.
colorsNoCap the number of colours.
detailNolow = bold and simple, medium = clean (default), high = closest to the picture.
layersNoobjects = each thing (hat, face...) as its own named, movable group, drawn whole underneath. +$0.02.
promptYesWhat to draw.
formatsNoExtra files: png, pdf, eps, dxf (cutting machines), icons (favicon pack zip), small.
objectsNoName the objects to separate, if you know them.
paletteNoSnap every colour to these (brand colours).
qualityNohd keeps finer detail: $0.15 instead of $0.05.
backgroundNotransparent removes a plain backdrop with no white ring.
include_svgNoPut the SVG markup in the reply. Off by default: traces are large.

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it reveals latency (8-60 s), a price band ($0.01-$0.25) with a pre-run quote, the default model, and the output character (editable real shapes, not a bitmap). It omits auth/rate-limit constraints and failure behavior, which keeps it from a 5.

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?

Roughly three sentences, front-loaded with the core purpose before model/cost/timing detail, and every sentence carries information about cost, default, or latency. The pricing clause is slightly dense but not wasteful.

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 14-parameter, no-annotation, no-output-schema tool, the description supplies the operational facts an agent most needs: what it produces, default behavior, cost, and duration. What comes back beyond 'a clean editable SVG' and error/retry behavior remains unstated, leaving a small gap.

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

Parameters4/5

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

Schema coverage is 100%, so the parameter baseline is 3, but the description adds cross-parameter meaning the schema does not: the cost range across models, the pre-execution price display, and the default-model fallback when 'model' is omitted. That is genuine added value over the enum descriptions.

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 a specific verb and resource: 'describe a picture and get a clean, editable SVG (real shapes, not a bitmap)'. The text-to-SVG framing implicitly separates it from the image-to-SVG sibling svg_vectorize, but no sibling is named explicitly, so it falls short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains model selection behavior ('Pick a model: amnt-auto picks the best one per request...; without one it uses AMNT Draw 1.2') and gives cost/latency, which helps an agent decide how to call it. However it never states when to prefer this tool over svg_vectorize or svg_library_search, so usage is only implied.

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

svg_library_getAInspect

Get the SVG code of one free AMNT library item by its slug (from svg_library_search). Free, no API key.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugYes

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it usefully discloses that the item is free and requires no API key, and that the operation is a retrieval of SVG code. It says nothing about behavior on an invalid/unknown slug, rate limits, or whether the item is cached, leaving gaps for a no-annotation tool.

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?

One sentence, front-loaded with the action and resource, with the lookup-key origin and auth/cost caveats appended compactly. No filler.

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 simple one-parameter retrieval with no output schema, the description covers what it returns (SVG code), the identifier source, and cost/auth. Only error behavior for a bad slug and any rate/usage limits are missing, which are minor for this tool's complexity.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It does explain that the single 'slug' parameter identifies a free AMNT library item and where to obtain it (svg_library_search), which is meaningfully more than the schema's bare 'type: string'. It still omits format expectations (case sensitivity, exact slug syntax).

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 (Get) and resource (SVG code of one AMNT library item) with the lookup key named. It also distinguishes itself from svg_library_search by noting the slug originates there, so an agent can route correctly without opening either 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?

The parenthetical '(from svg_library_search)' establishes the intended workflow (search first, then fetch the code), giving clear usage context. It does not state exclusions, e.g. that this is not for generating or vectorizing SVGs, which the sibling names svg_generate and svg_vectorize would otherwise require an agent to infer.

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

svg_vectorizeAInspect

AMNT SVG: turn an existing picture (PNG, JPEG or WebP: https URL, data: URI or base64) into a clean, editable SVG that keeps its shape and colours. Use this when you already have the image; to draw something new use svg_generate. Returns JSON with a link to the .svg, extra file links, size and a quality score (add include_svg: true for the markup). Price: $0.01; with "model": "amnt-vectorize-1.1" and "style": "logo" or "icon" a logo or icon comes back as tiny clean code ($0.08). Needs an AMNT API key; paid from Balance.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNocutout = no overlapping shapes, for Figma and cutting machines.
imageYesThe picture to convert: an https URL, a data: URI or raw base64 (PNG, JPEG or WebP).
modelNoThe AMNT model. Leave it out for AMNT Draw 1.2, the default. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into a clean SVG. Logos and icons come back as tiny clean code. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG. Every moving part is its own named group. Hand-drawn or flat.
styleNoWhat the picture is. logo and icon give the cleanest result (and with amnt-vectorize-1.1, a redraw as code).
colorsNoCap the number of colours.
detailNolow = bold and simple, medium = clean (default), high = closest to the picture.
layersNoobjects = each thing (hat, face...) as its own named, movable group, drawn whole underneath. +$0.02.
formatsNoExtra files: png, pdf, eps, dxf (cutting machines), icons (favicon pack zip), small.
objectsNoName the objects to separate, if you know them.
paletteNoSnap every colour to these (brand colours).
backgroundNotransparent removes a plain backdrop with no white ring.
include_svgNoPut the SVG markup in the reply. Off by default: traces are large.

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the auth requirement (AMNT API key, paid from Balance), concrete pricing per mode/style/model, the return shape (JSON with .svg link, extra file links, size, quality score), and a caveat (traces are large, hence include_svg is off by default).

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-loads the core purpose and the sibling routing, then adds return format and pricing. Efficient overall, though the pricing/quality details near the end partially repeat what the model enum already lists.

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 12-parameter tool with no output schema, the description fills the key gaps: it explains the return payload, the include_svg opt-in for markup, the auth/cost model, and routes correctly against svg_generate. Nothing an agent needs to invoke it correctly 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%, so the schema already documents all 12 parameters including model pricing and style/model interactions that the description restates. The description's added meaning (image input forms, the model+style cheap-logo combo) is marginal and largely duplicates enum descriptions.

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+resource ('turn an existing picture ... into a clean, editable SVG') and explicitly distinguishes itself from the sibling svg_generate ('to draw something new use svg_generate'). An agent can route between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the condition that selects this tool ('when you already have the image') and the alternative that selects the sibling ('draw something new'). Accepted input forms (https URL, data: URI, base64) are also stated up front.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedsvg_generate2 fields changed
      • changedInput schema / properties / model / description
        Previous value: -"The AMNT model. Leave it out for the classic drawn-then-traced SVG. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Drawn by AMNT Image, then traced clean: icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into SVG: logos and icons redrawn as clean code, the rest traced. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG: the parts that should move are drawn apart, named and animated. Hand-drawn or flat."New value: +"The AMNT model. Leave it out for AMNT Draw 1.2, the default. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into a clean SVG. Logos and icons come back as tiny clean code. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG. Every moving part is its own named group. Hand-drawn or flat."
      • addedInput schema / properties / quality / description
        Added value: +"hd keeps finer detail: $0.15 instead of $0.05."
    • Changedsvg_vectorize3 fields changed
      • changedInput schema / properties / image / description
        Previous value: -"An https URL, a data: URI or base64."New value: +"The picture to convert: an https URL, a data: URI or raw base64 (PNG, JPEG or WebP)."
      • changedInput schema / properties / model / description
        Previous value: -"The AMNT model. Leave it out for the classic drawn-then-traced SVG. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Drawn by AMNT Image, then traced clean: icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into SVG: logos and icons redrawn as clean code, the rest traced. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG: the parts that should move are drawn apart, named and animated. Hand-drawn or flat."New value: +"The AMNT model. Leave it out for AMNT Draw 1.2, the default. amnt-auto (AMNT Auto, $0.03): Picks the best AMNT model for each request. · amnt-svg-lite-1.1 (AMNT SVG Lite 1.1, $0.01): Simple icons, charts, patterns and flat backgrounds. Fastest and cheapest. · amnt-svg-1.1 (AMNT SVG 1.1, $0.03): Icons, logos, lettering, NFT bases and traits, as tiny clean SVG code. · amnt-svg-pro-1.1 (AMNT SVG Pro 1.1, $0.25): Characters, mascots and detailed art. The best NFT bases. · amnt-trace-1.2 (AMNT Draw 1.2, $0.05): Icons, logos, pixel art and illustrations with a few true colours. · amnt-vectorize-1.1 (AMNT Vectorize 1.1, $0.08): Turn your picture into a clean SVG. Logos and icons come back as tiny clean code. · amnt-animate-1.1 (AMNT Animate 1.1, $0.05): One prompt, a moving SVG. Every moving part is its own named group. Hand-drawn or flat."
      • addedInput schema / properties / style
        Added value: +{
+  "description": "What the picture is. logo and icon give the cleanest result (and with amnt-vectorize-1.1, a redraw as code).",
+  "enum": [
+    "auto",
+    "none",
+    "flat",
+    "icon",
+    "logo",
+    "illustration",
+    "pixel",
+    "hand-drawn",
+    "cartoon",
+    "kawaii",
+    "line-art",
+    "sticker",
+    "duotone"
+  ],
+  "type": "string"
+}
  2. 5 tool updates
    • First observedagents_search
    • First observedsvg_generate
    • First observedsvg_library_get
    • First observedsvg_library_search
    • First observedsvg_vectorize

Publisher details

Operator
amnt
Operator website
https://www.amnt.io · Publisher source
Vendor relationship
First-party
Documentation
https://www.docs.amnt.io · Publisher source
Trust center
https://www.amnt.io/terms · Publisher source
Restrictions
amnt.io/terms · Publisher source

Related MCP Connectors

Related MCP Servers

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