svgapp.ai

Initialize SVG App Config

init_svgapp_config

Read-onlyIdempotent

Create the local SVG App MCP config payload for this project.

Use when the repository does not have svgapp.conf.json, when the existing file is invalid, or when the client needs default artStyleId values.

Do not use when svgapp.conf.json already exists and has a valid artStyleId. In that case, read the file and reuse its artStyleId, colorPaletteId, and activeMascotId values.

Next tool to call: save or merge the returned config into svgapp.conf.json; then call create_color_palette if brand colors are needed, create_mascot for a reusable UI character, or generate_composition/create_generation for any standalone app illustration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "init_svgapp_config"
  }
}

Input Schema

Name	Required	Description	Default
`workspace`	No	Optional 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.

Output Schema

Name	Required	Description
`config`	Yes	Initial config object to save locally. Preserve unknown fields if merging with an existing file. Read this file before later generation calls.
`filename`	Yes	Always svgapp.conf.json; create it in the project root when missing, otherwise merge into the existing file.
`instructions`	Yes	Concrete file persistence instructions for the client.
`defaultArtStyle`	Yes	Default public art style id and name. Use config.artStyleId for generation tools.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description is consistent with them by stating the returned payload must be saved/merged by the caller rather than written in place. It adds real context beyond the annotations: what the payload contains (artStyleId, colorPaletteId, activeMascotId defaults) and where it belongs in the workflow. It stops short of describing the payload shape, though an output schema exists.

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?

Front-loaded with the action, then cleanly segmented into when-to-use, when-not-to-use, and next steps. Dense but nearly every clause carries actionable routing information; the final sentence chains several unrelated follow-ons, which is the only mild clutter.

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?

For a single-optional-parameter initializer with an output schema, the description supplies everything the agent needs: preconditions, the reuse-existing rule, and the downstream tool sequence. Return-value details are correctly left to the output schema.

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% on the single optional workspace parameter, and the schema description already explains defaulting to the personal workspace and the one-workspace-per-workflow rule. The tool description adds nothing about the parameter, so this lands at the baseline for fully documented schemas.

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?

Names a specific verb and resource ('Create the local SVG App MCP config payload') and immediately clarifies that this produces a payload rather than a file write, which separates it from the generation/palette/mascot siblings. An agent can tell what it produces and what it does not without opening the schema.

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?

Gives explicit trigger conditions (no svgapp.conf.json, file invalid, or client needs default artStyleId) and an explicit exclusion with the alternative behavior ('Do not use when svgapp.conf.json already exists and has a valid artStyleId. In that case, read the file and reuse...'). It then routes to the correct follow-on tools by condition (create_color_palette, create_mascot, generate_composition/create_generation).

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

All svgapp.ai tools Inspect

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.