Skip to main content
Glama

comfyui_get_model_presets

Read-onlyIdempotent

Fetch recommended generation presets for a model family from its filename or family ID, including sampler, scheduler, steps, CFG, and resolution.

Instructions

Get recommended generation presets for a model family.

    The presets are static data baked into this MCP — they reflect
    community best-practice defaults, not anything the connected ComfyUI
    server reports. At least one of ``model_name`` or ``model_family``
    must be supplied; if both are given, ``model_family`` takes
    precedence and ``model_name`` is ignored.

    Args:
        model_name (required if ``model_family`` is omitted): Model
            filename to auto-detect the family from (e.g.
            ``sd_xl_base_1.0.safetensors`` → ``sdxl``). Used as a
            fallback when ``model_family`` is empty.
        model_family (required if ``model_name`` is omitted): Explicit
            family identifier. Valid values: ``sd15``, ``sdxl``,
            ``flux``, ``sd3``, ``cascade`` (aliases like ``sd1.5``,
            ``stable-diffusion-xl``, ``flux.1``, ``sd3.5``,
            ``stable-cascade`` are also accepted).

    Returns:
        Dict ``{"family": "<id>", "recommended": {<settings>}}`` where
        ``recommended`` always contains the keys ``sampler`` (str),
        ``scheduler`` (str), ``steps`` (int), ``cfg`` (float),
        ``resolution`` (str like ``"1024x1024"``), ``clip_skip`` (int),
        and ``notes`` (str). Callers that only need the settings can
        read ``result["recommended"]`` directly.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_nameNo
model_familyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable behavioral detail: presets are baked into the MCP rather than fetched from the ComfyUI server, model_family takes precedence when both args are supplied, and the exact shape of the return value is specified. No contradiction with annotations.

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?

The description is well-structured with a short summary, Args section, and Returns section. Every sentence adds useful information—precedence, static data source, return keys—without redundancy or filler. It is detailed but appropriately sized for the tool's complexity.

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?

The description is complete for this tool: it covers purpose, data source, parameter semantics, edge-case precedence, and return format. Even though an output schema exists, the description's explicit return structure helps callers know exactly which keys are available.

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

Parameters5/5

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

The input schema provides no descriptions (0% coverage), so the description fully compensates by explaining each parameter, including valid family identifiers, accepted aliases, requiredness conditions, and an example filename-to-family mapping. This is far beyond baseline.

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 opens with a specific verb-object pair: 'Get recommended generation presets for a model family.' This clearly distinguishes it from sibling tools like comfyui_get_model_metadata or comfyui_get_prompting_guide by stating exactly what resource it returns and for what purpose.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool: it returns static community presets and requires at least one of model_name or model_family, with precedence rules. However, it does not explicitly mention when not to use it or name alternative tools, so it stops short of the highest bar.

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/hybridindie/comfyui_mcp'

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