Skip to main content
Glama
Sign In

svgapp.ai

by io.github.Xyz3R
OverviewDiscussionsAdmin

List Art Styles

list_art_styles
Read-onlyIdempotent

List available SVG App art styles.

Use when svgapp.conf.json is missing, the user asks to choose a style, or a generation tool needs artStyleId recovery.

Do not use as part of every generation if svgapp.conf.json already has a valid artStyleId.

Next tool to call: create_mascot, generate_composition, or create_generation with the selected artStyleId.

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": "list_art_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Output Schema

NameRequiredDescriptionDefault
artStylesYesAvailable art style id/name pairs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the non-obvious behavioral role of this tool as a config-recovery step and warns against redundant calls. It stops short of describing ordering, caching, or the shape of the returned style entries, which the output schema carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences/blocks: what it does, when to use it (with the exclusion), then the routing instruction. The key constraint is front-loaded and every sentence earns its place.

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 present, the description need not explain return values, and it fully covers the workflow position and prerequisites. The only minor gap is that it does not state whether the style list itself is workspace-scoped, despite the workspace parameter implying scoping.

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?

There is a single optional 'workspace' parameter and schema description coverage is 100%, so the schema already explains the id/slug source, the personal-workspace default, and the consistency requirement. The description adds no additional meaning about the parameter, which is the expected baseline when the schema is complete.

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 first sentence names a specific verb and resource ('List available SVG App art styles') and the follow-up names the concrete outputs (artStyleId) it supplies to sibling tools. An agent can tell this apart from list_workspaces, list_mascots, and the generation tools 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?

It gives three explicit triggers (svgapp.conf.json missing, user asks to choose a style, artStyleId recovery), an explicit negative case (do not call on every generation when a valid artStyleId exists), and names the next tools to route to. This is the full when/when-not/alternatives pattern.

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