Skip to main content
Glama

list_available_presets

Retrieve available style presets for AI-powered 2D game asset generation in ComfyUI workflows.

Instructions

List all available style presets for asset generation.

Returns:
    JSON object containing all presets with their configurations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool() decorated handler function for list_available_presets. It calls the helper list_presets() and returns the result as formatted JSON string.
    @mcp.tool()
    async def list_available_presets() -> str:
        """List all available style presets for asset generation.
        
        Returns:
            JSON object containing all presets with their configurations
        """
        return json.dumps(list_presets(), indent=2)
  • Helper function that converts the PRESETS dictionary into a serializable format for the tool response.
    def list_presets() -> Dict[str, Dict[str, Any]]:
        """List all available presets."""
        return {name: preset.to_dict() for name, preset in PRESETS.items()}
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the return format ('JSON object containing all presets with their configurations') but lacks critical details like whether this is a read-only operation, if there are rate limits, authentication requirements, or how the data is structured. The description is insufficient for a tool with zero annotation coverage.

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?

The description is appropriately concise with two sentences that directly address purpose and return format. It's front-loaded with the core function. The second sentence about returns could be integrated more smoothly, but overall it's efficient with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has zero parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, with no annotations and multiple sibling generation tools, it should better explain how this listing tool integrates with the generation workflow. The presence of an output schema means it doesn't need to detail return values, but broader context is lacking.

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 has zero parameters, and schema description coverage is 100% (though empty). The description appropriately doesn't discuss parameters since none exist. It could slightly improve by explicitly stating 'no parameters required' but this is minor. Baseline for zero parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('all available style presets for asset generation'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'generate_character' or 'generate_sprite' beyond the list vs generate distinction, which is why it doesn't reach a perfect 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or relationships to sibling tools like 'generate_character' (which might use these presets). The agent must infer usage context independently.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuannguyen14/ComfyAI-MCP-GameAssets'

If you have feedback or need assistance with the MCP directory API, please join our Discord server