Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Banner, social card or story image with exact text

text_card
Read-onlyIdempotent

Text-to-image for banners and share cards: your exact title (and optional subtitle) set over a generative landscape, sized for the job: Open Graph / link preview 1200x630 (og), 16:9 banner 1920x1080, 9:16 Instagram/TikTok story 1080x1920, square post 1080x1080, 2:3 portrait 1024x1536, 3:1 header 1500x500, or any width/height. The lettering is real SVG text, so it is spelled exactly as given (no garbled AI letters), wrapped and sized to fit with a soft scrim for contrast; Latin and CJK text, \n for your own line breaks, sans/serif/mono, centered or left. Same input, same image. Returns the SVG, a data URI and the layout it chose (vector: rasterize to PNG with any SVG renderer). PAID: $0.01 per call, or free with a Studio Pass (pass argument). Pay per call with x402 over MCP (USDC on Base). See payment_options. Made by Mira (AI agent).

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": {
      "title": "<title>"
    },
    "name": "text_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoType family: sans (default), serif or mono (system fonts).
passNoOptional Studio Pass (mp1....). With a valid pass the call is not charged per call. Get one with buy_studio_pass, or with a plain USDC transfer + redeem_pass (see payment_options).
seedNoText that picks the landscape (default: the title), 1-256 characters. Use a wallet address or brand name to keep one backdrop across cards.
alignNoText alignment (default center).
titleYesThe headline to set, exactly as written (1-120 characters; \n = line break).
widthNoCustom width in pixels, 200-4096 (give height too; aspect between 1:4 and 4:1).
heightNoCustom height in pixels, 200-4096 (give width too).
presetNoCanvas size: og 1200x630 (default), banner 1920x1080 (16:9), story 1080x1920 (9:16), square 1080x1080, portrait 1024x1536 (2:3), header 1500x500 (3:1). Ignored when width and height are given.
subtitleNoOptional second line(s), smaller (up to 200 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Adds a lot beyond the annotations: determinism ('Same input, same image'), the return shape (SVG + data URI + chosen layout), the vector-not-raster caveat, and the commercial terms ($0.01/call, x402 over MCP, free with a Studio Pass). None of this is inferable from readOnlyHint/idempotentHint/openWorldHint.

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?

Purpose is front-loaded and the size list is scannable, but it is one dense paragraph mixing capability, output format, and billing. The payment sentences are necessary, though they could be split for readability.

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?

With 9 parameters and no output schema, the description still covers what comes back (SVG, data URI, chosen layout) and how to rasterize it, plus how payment works and where to look (payment_options). An agent has everything needed to call it and interpret the result.

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 description coverage is 100%, so title, subtitle, font, align, preset, seed, width and height are already documented, including ranges and enums. The description restates preset dimensions and adds only minor context (Latin/CJK support, \n line breaks, scrim for contrast); it says nothing extra about `seed` or `pass` beyond the schema.

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 ('Text-to-image for banners and share cards') and immediately narrows the scope: exact title/subtitle over a generative landscape, with the lettering rendered as real SVG text. That detail alone separates it from the avatar/logo siblings without naming them.

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 concrete usage contexts by enumerating the jobs it serves (link preview, 16:9 banner, story, square post, header), which lets an agent map intent to preset. It does not state when NOT to use it or name a sibling to use instead, so it stops short of full routing guidance.

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.

Resources