Skip to main content
Glama
Sign In

svgapp.ai

by io.github.Xyz3R
OverviewDiscussionsAdmin

List Workspaces

list_workspaces
Read-onlyIdempotent

List the SVG App workspaces the signed-in user can use, with workspaceId, slug, name, and whether it is the personal workspace.

Use when the user wants to generate into a team workspace instead of their personal one, or when a tool reports that a workspace was not found.

Next tool to call: pass the chosen slug or workspaceId as the workspace argument of the other tools. Omit workspace to use the personal workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
workspacesYesWorkspaces with workspaceId, slug, name, and isPersonal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely non-redundant behavior: that the list is scoped to the signed-in user, and that omitting the workspace argument downstream defaults to the personal workspace. It stops short of noting ordering, pagination, or what an empty list means, which keeps it below a 5.

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, front-loaded blocks: what it returns, when to call it, and what to do with the result. Every sentence carries distinct information with no restatement of the title or annotations.

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 parameterless, read-only discovery tool with annotations and an output schema already present, the description covers everything an agent needs: purpose, invocation triggers including the error-recovery path, and how to consume the result. No material gap remains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is nothing for the schema to document. The description still adds value by explaining how the returned slug/workspaceId feeds the 'workspace' argument of other tools and what omitting that argument implies.

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?

States a specific verb and resource ('List the SVG App workspaces') and names the exact fields returned (workspaceId, slug, name, personal flag), so the agent knows what it gets without opening the output schema. It is clearly distinct from the creation/generation siblings, which all produce assets rather than enumerate workspace scope.

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 two explicit triggers: the user wants to target a team workspace, or another tool reports a workspace was not found. It also closes the loop by naming the next action (pass slug/workspaceId as the workspace argument, or omit it for personal), 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