Skip to main content
Glama
Sign In

svgapp.ai

by io.github.Xyz3R
OverviewDiscussionsAdmin

Create UI Color Palette

create_color_palette

Create a reusable SVG App color palette for generated mascots, mascot poses, and UI illustrations.

Use when the user asks for generated assets that should match an app, SaaS product, brand, design system, landing page, dashboard, or specific UI color direction.

Do not use when the project already has a suitable colorPaletteId in svgapp.conf.json or when color consistency is irrelevant.

Next tool to call: merge configPatch.colorPaletteId into svgapp.conf.json, read the updated file, then call create_mascot, generate_mascot_pose, generate_composition, or create_generation.

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>",
      "backgroundColor": "<backgroundColor>",
      "primaryColor": "<primaryColor>",
      "accentColor": "<accentColor>"
    },
    "name": "create_color_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShort human-readable palette name, for example 'Acme Dashboard Palette'.
workspaceNoOptional workspace id or slug from list_workspaces. Defaults to the user's personal workspace. Use the same workspace for every call in a workflow, because generations, mascots, and palettes belong to one workspace.
accentColorYesSecondary accent color as #RRGGBB. Use this for contrast, highlights, or supporting UI details.
customColorsNoOptional named extra brand colors the generation should respect, such as success, warning, chart, or mascot-specific colors.
primaryColorYesPrimary brand/action color as #RRGGBB. Use the product's main CTA or brand color.
backgroundColorYesMain UI background color as #RRGGBB. Use the app canvas/page background or a neutral surface color.

Output Schema

NameRequiredDescriptionDefault
configPatchYesMerge this into svgapp.conf.json.
instructionsYesNext persistence step for the client.
colorPaletteIdYesPalette id to use as colorPaletteId in generation tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds genuinely useful behavior beyond that: the palette must be merged into svgapp.conf.json via configPatch.colorPaletteId and the updated file read before generation tools are called. It stops short of explaining that repeated calls may create duplicate palettes (consistent with idempotentHint=false) or what permissions are needed.

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?

The three short paragraphs are front-loaded with purpose, then exclusions, then the follow-up workflow, which is the right order for an agent. The instruction sentence is slightly long with four alternative follow-on tools, but each element carries actionable information and no sentence is 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?

With an output schema and full schema description coverage, the description need not explain return values, and it covers the key workflow context an agent needs before calling. The only minor gap is that idempotency and duplicate-prevention expectations are left implicit rather than stated.

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 every parameter — name, workspace, accentColor, customColors, primaryColor, backgroundColor — is already documented with hex format and intent. The description adds no parameter-level syntax or constraints beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource — 'Create a reusable SVG App color palette' — and scopes it to generated mascots, poses, and UI illustrations. This clearly separates it from siblings like create_mascot or create_generation, which consume the palette rather than define it.

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?

It states explicitly when to use it (matching an app, brand, design system, landing page, or UI direction) and when not to (a suitable colorPaletteId already exists, or color consistency is irrelevant). It also names the exact next tool calls, leaving nothing to inference.

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

All svgapp.ai toolsInspect
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