Skip to main content
Glama
Whambammy

Vector Graphics Pipeline MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BASE_RPC_URLYesBase L2 RPC URL
PAYMENT_WALLETYesRecipient payout wallet address on Base L2

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
optimize_vector_svgA

Strips bloated XML, cleans SVG nodes, converts paths for direct cutting, sublimation, and high-performance web graphics. (0.02 USDC on Base L2)

convert_svg_to_pngB

Deterministic SVG to PNG rasterizer with crisp sub-pixel antialiasing, custom DPI, and transparent alpha channel preservation. (0.015 USDC on Base L2)

generate_qr_code_svgA

Generates high-precision scalable vector (SVG) QR codes with High error correction (ECC Level H), tailored for Base payment URIs. (0.01 USDC on Base L2)

compress_image_webpA

Serverless WebP image compressor: optimizes alpha channels, strips privacy-invasive EXIF tags, and cuts image weight by 80%. (0.025 USDC on Base L2)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a distinct action and target format: SVG optimization, SVG-to-PNG rasterization, QR SVG generation, and WebP compression. The two SVG-producing/consuming tools (optimize_vector_svg, generate_qr_code_svg) could be briefly confused, but their verbs make intent clear.

Naming Consistency5/5

All four names follow a strict verb_object snake_case pattern (optimize_..., convert_..., generate_..., compress_...). Naming is fully predictable and consistent.

Tool Count4/5

Four tools is on the lean side but reasonable for a focused, paid micro-service pipeline. Each tool earns its place, though the surface feels slightly thin for a 'pipeline'.

Completeness3/5

Core operations are present, but the surface has notable gaps: no raster-to-vector conversion, no resizing/other format conversions (e.g. to PDF), and no batch processing. Also compress_image_webp handles raster images, drifting from the stated vector-graphics scope.

Maintenance

ActivityMaintained
ResponsivenessNo issues