Skip to main content
Glama

check_workflow_runtime

Determine whether a workflow runs locally (free) or uses paid API nodes. Scans node class types and returns runtime status to avoid unexpected credit use.

Instructions

Determine whether a workflow runs on the user's OWN GPU (LOCAL — free) or uses hosted API NODES (PAID api credits). Pass pack (a bundled pack name — always local/free) OR graph (a UI or API/prompt workflow JSON, as object or string). It scans the workflow's node class_types against the connected ComfyUI's API-node set (the same signal list_api_nodes uses) and returns { runtime: 'local'|'api'|'mixed'|'unknown', usesApiNodes, apiNodes[], unknownNodes[] } — 'unknown' means some nodes couldn't be classified (could be paid), so treat it (and 'api'/'mixed') as POSSIBLY PAID; only 'local' is confirmed free. ALWAYS call this before building OR loading a non-pack/ad-hoc workflow so you can ASK the user before spending paid API credits — never silently use API nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packNoA bundled pack name (from list_packs). Packs are local/free; this confirms it from the actual graph.
graphNoA workflow graph to classify (UI or API/prompt format), as an object or a JSON string. Use this for ad-hoc/generated workflows.
Behavior5/5

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

With no annotations, the description fully covers behavioral details: scans node class types, returns classification with flags, clarifies that 'unknown' means possibly paid, and only 'local' is confirmed free. Also explains cost implications. No contradictions.

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?

Description is well-structured and efficient, with first sentence stating purpose, then parameters, return value, and usage guidance. Minor redundancy in restating 'packs are local/free' after already mentioning it, but overall no waste.

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?

Despite no output schema, the description fully explains the return value shape and interpretation, including handling of 'unknown'. It also covers usage rules thoroughly. Complete for a classification tool with two parameters.

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?

Schema coverage is 100%, but description adds value: explains that pack is for bundled packs (always local/free) and graph is for ad-hoc workflows. Also clarifies that pack confirms from actual graph and describes the expected formats (object or string for graph).

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 tool determines whether a workflow runs locally (free) or uses API nodes (paid), with specific verb 'determine whether' and resource 'workflow runtime'. It distinguishes itself from siblings by focusing on classification rather than generation, and references list_api_nodes for context.

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: 'ALWAYS call this before building OR loading a non-pack/ad-hoc workflow'. Provides clear alternatives: packs are always local/free, so skipping is possible. Emphasizes asking user before spending credits, and implies not to use API generation tools without checking.

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

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