CNAPS.ai MCP Server

get_flow

Read-onlyIdempotent

Read a flow. Pick the view that answers the question: 'detail' (default) for the raw nodes, connections and parameters — use this to discover node IDs; 'summary' for a plain-language description of what the flow does; 'status' for execution state and output file URLs — a running node's wait.phase tells queued (waiting for a GPU, with jobs ahead) from loading_model, starting, generating and finishing; 'validation' for pre-run problems (trashed, running, missing inputs, disconnected nodes). To follow a run, call view='status' with wait_seconds=20: the call returns as soon as the run ends, or after 20 seconds with the run still going — then call it again. No need to sleep between calls.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "flow_id": "<flow_id>"
    },
    "name": "get_flow"
  }
}

Input Schema

Name	Required	Description
`view`	No	One of: detail (default), summary, status, validation.
`flow_id`	Yes	The unique identifier of the flow.
`wait_seconds`	No	view='status' only: seconds to wait for a running flow to finish before answering (max 20, default 0). A flow that is not running answers at once.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / wait_seconds

Added value: +{
+  "description": "view='status' only: seconds to wait for a running flow to finish before answering (max 20, default 0). A flow that is not running answers at once.",
+  "type": "number"
+}

Changed1 schema field changedAug 9, 2026

addedInput schema / properties / view

Added value: +{
+  "description": "One of: detail (default), summary, status, validation.",
+  "type": "string"
+}

First observedAug 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it discloses the polling contract (returns as soon as the run ends or after the timeout with the run still going), explains that a non-running flow answers at once, and decodes wait.phase values (queued with jobs ahead vs loading_model, starting, generating, finishing).

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?

Front-loaded with the core action and view selection, and nearly every sentence carries new information. The view menu is packed into one long semicolon-and-em-dash sentence that would scan faster as a short list, which is the only structural cost.

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?

There is no output schema, and the description compensates by characterizing the payload of each view (raw nodes/connections/parameters, plain-language summary, execution state and output URLs, validation problems). Combined with the polling instructions, an agent has everything needed to call and re-call it correctly.

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?

Schema coverage is 100% and the schema already names all four view values and the wait_seconds max/default, so the baseline is 3. The description still adds real meaning by explaining what each view returns and why you would pick it, plus the wait/retry behavior of wait_seconds, though it stops short of syntax or error semantics for flow_id.

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?

Opens with a specific verb+resource ('Read a flow') and immediately partitions the tool into four named views with distinct content, so an agent can tell it apart from siblings like preview_flow, list_flows and edit_flow without opening a schema.

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?

Explicit per-view routing: 'detail' to discover node IDs, 'summary' for plain-language description, 'status' for execution state and output URLs, 'validation' for pre-run problems. It also prescribes the exact follow-up loop (view='status' with wait_seconds=20, then call again) and states no sleep is needed between calls.

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

All CNAPS.ai MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?