Skip to main content
Glama
IO-AtelierTech

ComfyUI MCP Server

by IO-AtelierTech
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

refresh_nodes

Updates the node cache to detect newly installed custom nodes in ComfyUI workflows.

Instructions

Refresh the node cache.

    Call this after installing new custom nodes to see them in list_nodes().

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/comfy_mcp_server/tools/discovery.py:160-173 (handler)
    The main handler function for the 'refresh_nodes' tool. It refreshes the ComfyUI node cache by clearing it and reloading the node list, then returns a confirmation message with the count of available nodes.
    @mcp.tool()
def refresh_nodes(ctx: Context = None) -> str:
    """Refresh the node cache.

    Call this after installing new custom nodes to see them in list_nodes().
    """
    if ctx:
        ctx.info("Refreshing node cache...")
    clear_node_cache()
    try:
        nodes = get_cached_nodes()
        return f"Cache refreshed. {len(nodes)} nodes available."
    except Exception as e:
        return f"Error refreshing cache: {e}"

Tool Definition Quality

A4.4/5.0
Behavior3/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 describes the cache-refresh behavior and its effect on list_nodes, but doesn't mention potential side effects like performance impact, whether it's idempotent, or error conditions. It adds useful context but lacks comprehensive behavioral disclosure.

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?

Two sentences with zero waste. First sentence states the core action, second provides essential usage context. Perfectly front-loaded and appropriately sized for a simple tool.

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

Completeness4/5

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

For a zero-parameter tool with no annotations or output schema, the description provides complete enough context about when and why to use it. It could benefit from mentioning what 'refreshing' entails or confirmation of success, but covers the essentials well.

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 coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's purpose and usage context.

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 description clearly states the specific action ('Refresh') and resource ('node cache'), distinguishing it from siblings like 'list_nodes' or 'add_node'. It explains the tool's purpose is to update the cache after installing new custom nodes.

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?

Explicitly states when to use this tool: 'after installing new custom nodes to see them in list_nodes()'. This provides clear context and distinguishes it from alternatives like directly calling list_nodes without refreshing.

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/IO-AtelierTech/comfyui-mcp'

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