Skip to main content
Glama

list_workflows

Read-only

Lists available ComfyUI workflows and their adjustable inputs, helping you pick a workflow and identify which values to change before rendering.

Instructions

Your own ComfyUI workflows (API-format .json files in the workflows folder) and the inputs each one lets you change (prompt, image, seed, steps... found automatically, or nodes titled "$name" in ComfyUI).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_workflows"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine context: the source location (workflows folder), the file format (API-format .json), and the discovery rule for inputs, both automatic detection and "$name" node titles. It says nothing about ordering, error handling when the folder is empty, or pagination.

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?

A single compact sentence with parenthetical detail, so there's no padding to trim. It leads with the resource rather than a verb, which makes it slightly less front-loaded for an agent scanning for an action.

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?

With no output schema, the description must convey the return shape, and it does: a set of the user's own workflows plus the changeable inputs for each. For a parameterless read-only list tool that's close to sufficient; only ordering and empty-folder behavior are unstated.

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 takes zero parameters, so there are no argument semantics to explain and the baseline of 4 applies. The parenthetical still clarifies what the discovered inputs look like, which is a helpful supplement.

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 concretely identifies the resource (ComfyUI workflow .json files in the workflows folder) and the payload (the per-workflow editable inputs), so an agent knows exactly what comes back. It stops short of a clean verb-first statement and doesn't distinguish itself from siblings such as check_workflow.

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?

It describes content but never says when to call it, when not to, or which sibling (e.g. check_workflow, list_models) to prefer for a related need. The intended use, discovering runnable workflows, is only faintly inferable from the phrasing.

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