Skip to main content
Glama

comfyui_get_prompting_guide

Read-onlyIdempotent

Get prompting guidance for SD1.5, SDXL, Flux, SD3, or Cascade models, including prompt structure, weighting syntax, quality tags, and negative prompt tips.

Instructions

Get the prompting guide for a model family.

    The guide is static data baked into this MCP — it gives stylistic
    and structural advice tuned to each family (prompt structure,
    weighting syntax conventions, recommended quality tags, negative
    prompt tips). It does not reflect the connected ComfyUI server's
    installed models or state.

    Args:
        model_family (required): 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>", "guide": {<advice>}}`` where ``guide``
        always contains the keys ``prompt_structure`` (str),
        ``weight_syntax`` (str), ``quality_tags`` (list[str]), and
        ``negative_prompt_tips`` (str). Callers that only need the
        advice can read ``result["guide"]`` directly.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
model_familyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds that the data is baked into the MCP and always returns a guide with specific keys, and advises reading result['guide'] directly, which clarifies the return behavior beyond the annotations. It does not describe error handling for invalid family identifiers, but the parameter guidance mitigates that.

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 structured with a one-sentence summary, a short explanatory paragraph, and labeled Args/Returns sections. Every sentence adds either purpose, context, or parameter guidance without fluff.

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?

Given that this is a simple static lookup tool with one parameter, the description covers the parameter values, the static nature, and the exact return shape. It even includes a usage tip for reading the guide directly, making it sufficiently complete for an agent to invoke the tool correctly.

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 only the parameter name and title with no description or enum, so schema coverage is 0%. The description compensates by listing all valid family identifiers and accepted aliases (sd15, sdxl, flux, etc.), giving the agent actionable syntax and exact accepted values.

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 'Get the prompting guide for a model family,' which combines a specific verb and resource. It further clarifies that the guide is static and separate from server state, distinguishing it from sibling tools like get_model_metadata or get_server_features.

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 the context that this tool returns static data and explicitly notes that it does not reflect the connected server's installed models or state. This tells the agent when not to expect dynamic information, but it does not name alternative tools for server-specific data, so the guidance is helpful but not fully explicit.

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