Skip to main content
Glama
Sign In

svgapp.ai

by io.github.Xyz3R
OverviewDiscussionsAdmin

List Recent Generations

list_recent_generations
Read-onlyIdempotent

List recent SVG App generations in the selected workspace with generationId, status, imageUrl or videoUrl when available, and nextAction.

Use when the client lost a generationId, wants to recover recently created mascots/poses/compositions, or needs to inspect current async work without relying on MCP resources.

Do not use as the normal polling path for a known generationId; use get_generation_status for that.

Next tool to call: call get_generation_status for a pending generation, get_generated_asset for a completed generation, or generate_mascot_pose when a completed mascot should be reused in a UI-specific pose.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum number of recent generations to return. Defaults to 10 and is capped at 50.
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
generationsYesRecent generations with generationId, status, imageUrl when ready, and nextAction.

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the shape of what comes back and the fact that this is a substitute for MCP resources. It stops short of stating ordering (newest-first?) or how many items a capped list may silently omit, which is the one behavioral gap.

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 what, then when/when-not, then next-step routing – an easy scan for an agent. Slightly verbose in the third paragraph (the get_generated_asset and generate_mascot_pose branches are arguably derivable), but every sentence carries routing information.

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?

An output schema exists, so return-value documentation is not required, yet the description still summarizes the key fields. Combined with explicit sibling routing and use/exclusion guidance, an agent has everything needed to call this correctly in a workflow.

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% and both parameters already document their defaults, caps, and workspace-id-or-slug semantics. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 recent SVG App generations in the selected workspace') and enumerates the returned fields (generationId, status, imageUrl/videoUrl, nextAction). This is clearly separable from get_generation_status, which targets a known id.

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 three concrete when-to-use triggers (lost generationId, recovering recently created mascots/poses/compositions, inspecting async work without resources), an explicit when-not ('Do not use as the normal polling path for a known generationId'), names the alternative, and adds next-tool routing.

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