Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Logo kit: logo, palette, favicon from a name

logo_kit
Read-onlyIdempotent

Logo maker and brand kit in one call: give a brand or product name (and an optional tagline) and get a flat SVG logo mark (a small generative landscape: sky, sun or moon, hills / peaks / dunes / mesas / isles), a monogram app icon from the initials, horizontal and stacked logo lockups with the name set as real SVG text (spelled exactly as given), a favicon, a 1200x630 Open Graph share card, a brand color palette (primary, secondary, ink, paper, sky) with WCAG contrast ratios, CSS variables and a heading/body font pairing. All colors come from one scene, so the pieces match. Same name, same kit. Vector SVG; rasterize to PNG with any SVG renderer. PAID: $0.03 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": {
      "name": "<name>"
    },
    "name": "logo_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fontNoHeading type family for the name: sans (default), serif or mono (system font stacks).
nameYesBrand, product or project name, exactly as it should be spelled (1-40 characters).
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 scene and colors (default: the name), 1-256 characters. Try another seed for a different mark with the same name.
shapeNoOutline of the mark, monogram and favicon: circle (default), rounded (app-icon square) or square.
taglineNoOptional tagline shown under the name in the lockups and on the share card (up to 80 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?

Annotations already declare readOnly/idempotent/closed-world, and the description layers on what they cannot: a per-call price ($0.03), the free-with-Studio-Pass path, the x402/USDC-on-Base payment mechanism, and that the call succeeds only with a pass or payment. It also discloses determinism ('Same name, same kit') and output format (vector SVG, rasterize downstream), which materially affect how an agent should invoke and consume it.

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?

It is a single dense paragraph, but it is front-loaded with the core promise and the output inventory before pricing and attribution. Nearly every clause carries information; the only near-filler is the 'Made by Mira (AI agent)' sign-off, which slightly dilutes an otherwise efficient block.

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 no output schema, the description carries the full burden and does so: it describes every returned artifact, the palette roles, the contrast data, and the SVG-not-PNG format. Payment prerequisites are covered and routed to sibling tools, so an agent has everything needed to call it correctly on the first try.

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% and the schema already documents name, tagline, seed, pass, shape and font with enums and length bounds. The description mainly restates 'name (and an optional tagline)' and adds little parameter-specific detail beyond hinting that seed drives scene/color selection, which is already spelled out in the schema. Baseline 3 is the right ceiling here.

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?

The description opens with a specific verb+resource ('Logo maker and brand kit in one call') and then enumerates every artifact produced: SVG mark, monogram app icon, horizontal/stacked lockups, favicon, OG card, palette with contrast ratios, CSS variables, font pairing. An agent can tell exactly what it gets, and the shape of the output (generative landscape scene) distinguishes it from a generic image generator.

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?

It states the input needed ('give a brand or product name'), the determinism contract ('Same name, same kit'), and that colors all derive from one scene, which tells an agent when this tool fits a whole brand-kit request rather than a single asset. It does not explicitly exclude or name alternatives such as vista_avatar or text_card, and the only redirects are for payment (payment_options, buy_studio_pass, redeem_pass).

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