Skip to main content
Glama

list_official_templates

Retrieve official ComfyUI workflow templates from the Comfy-Org repository, synced and converted to DSL format for workflow management.

Instructions

List official ComfyUI templates.

Returns templates from the official Comfy-Org repository that have been synced and converted to DSL format.

Returns: List of official template metadata

Examples: list_official_templates()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function decorated with @mcp.tool, which implements the list_official_templates tool by calling template_manager.search_templates(source='official') to retrieve official template metadata.
    @mcp.tool
    def list_official_templates() -> list[dict]:
        """List official ComfyUI templates.
        
        Returns templates from the official Comfy-Org repository
        that have been synced and converted to DSL format.
        
        Returns:
            List of official template metadata
        
        Examples:
            list_official_templates()
        """
        try:
            # Get only official templates
            results = template_manager.search_templates(source="official")
            return results
            
        except Exception as e:
            raise ToolError(f"Error listing official templates: {e}")
  • The @mcp.tool decorator registers the list_official_templates function as an MCP tool.
    @mcp.tool
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the source (official Comfy-Org repository) and format (DSL), but doesn't disclose behavioral traits like whether it's read-only, pagination, rate limits, authentication needs, or what 'synced' entails. The description adds some context but lacks critical operational details.

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 sized and front-loaded, starting with the core purpose. The 'Returns' and 'Examples' sections add value without redundancy. However, the example 'list_official_templates()' is somewhat redundant with the name, slightly reducing efficiency.

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 0 parameters, 100% schema coverage, and an output schema exists, the description is moderately complete. It explains what the tool does and the source/format, but as a list operation with no annotations, it should more explicitly state it's a read-only fetch and clarify the return structure beyond 'metadata', despite the output schema covering details.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters, and it correctly indicates no inputs are required by including an example with empty parentheses. No additional parameter semantics are needed or provided.

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 'official ComfyUI templates', specifying they come from the official Comfy-Org repository and are synced/converted to DSL format. It distinguishes from generic 'list_templates' by focusing on official ones, though doesn't explicitly contrast with 'search_templates' or other siblings.

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?

No guidance on when to use this tool versus alternatives like 'list_templates' or 'search_templates'. The description implies it's for official templates only, but doesn't specify use cases, prerequisites, or exclusions. It's left to the agent to infer context from sibling names.

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/christian-byrne/comfy-mcp'

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