Skip to main content
Glama
Sign In

svgapp.ai

by io.github.Xyz3R
OverviewDiscussionsAdmin

List Mascots

list_mascots
Read-onlyIdempotent

List existing reusable SVG App mascots in the selected workspace.

Use when the user wants a new pose for an existing mascot but svgapp.conf.json has no activeMascotId, or when the client needs to recover/select mascotId.

Do not use for standalone illustrations. Do not use when activeMascotId is already known and valid.

Next tool to call: generate_mascot_pose with the selected mascotId, or create_mascot if no suitable mascot exists.

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_mascots"
  }
}

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
mascotsYesExisting mascot id/name/description records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds workflow-level behavior the annotations cannot: that this is the recovery/selection step in a mascot pipeline and which tools consume its output. It stops short of describing result ordering or empty-list behavior, and an output schema exists to cover the return shape.

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?

Purpose is front-loaded in the opening sentence, followed by use conditions, exclusions, and the next tool in that order. Every sentence carries routing information — none is filler or a restatement of the name.

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-param read tool with full annotations and an output schema, an agent needs only to know why to call it and what to do next — both are supplied, including the branch for the no-suitable-mascot case. There is no meaningful gap left for the description to fill.

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 one optional parameter with 100% schema description coverage, including its default and the cross-call workspace consistency rule, so the schema does the heavy lifting. The description only echoes "in the selected workspace" and adds no syntax or format detail beyond that. Baseline 3 is appropriate 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 first sentence states a specific verb and resource ("List existing reusable SVG App mascots") and scopes it to the selected workspace. It explicitly excludes standalone illustrations, so an agent can distinguish this from list_recent_generations or get_generated_asset without opening a 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?

The description gives explicit trigger conditions (user wants a new pose but activeMascotId is missing, or the client needs to recover/select a mascotId), explicit exclusions (no standalone illustrations; skip when activeMascotId is already valid), and names the follow-up tools (generate_mascot_pose, create_mascot). Nothing about when to pick this tool is left 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