Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Svg generate

svg_generate
Read-onlyIdempotent

Generate a clean, sanitized standalone SVG vector graphic (icon, logo, badge, or diagram) from a text prompt. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": {
      "prompt": "<prompt>"
    },
    "name": "svg_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoOptional style: minimal (default), flat, outline, badge, diagram, or geometric.
widthNoOptional width in px (32-1024, default 256).
heightNoOptional height in px (32-1024, default 256).
promptYesDescription of the SVG vector icon, logo, badge, or diagram to draw (3-1000 chars).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description usefully adds the paid-call model, exact pricing ($0.002/call), accepted chains/tokens (USDC on Arc/Base/Solana, XNT on X1), and the guarantee of sanitized standalone output. No contradiction with the annotations, and 'sanitized' is a meaningful quality/security disclosure. Missing: failure behavior when payment is insufficient, and whether retries double-charge given idempotentHint.

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?

Three tight sentences, front-loaded with the capability, then economics, then the call protocol — a sensible order with no filler. The parenthetical chain list is dense but earns its place by preventing a payment-rail mistake.

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?

With five parameters, no output schema, and generation semantics, the description covers what an agent needs to invoke it: what it makes, what it costs, and how to pay. The one real gap is the return shape — it never says whether the response contains SVG markup directly or a URL/reference, leaving the agent to infer output handling after the call.

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 prompt/style/width/height/payment are all documented in structured fields; the baseline is 3. The description does add the `payment` semantics (signed x402 payload, obtained from the first unpaid call), which the schema only names, but it adds nothing about style or dimension tradeoffs beyond what the schema states.

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 — 'Generate a clean, sanitized standalone SVG vector graphic' — and enumerates concrete artifacts (icon, logo, badge, diagram). The word 'SVG' plus 'sanitized' implicitly separates it from the raster-oriented sibling image_generate without needing to name it.

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 an explicit operating procedure: 'Call once without `payment` for terms, then call again with `payment`.' That is real sequencing guidance an agent would otherwise get wrong. It stops short of stating when to prefer this over image_generate or what to do if the first call's terms are rejected.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.