Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

listWorkflowNodes

List every node in a specified workflow graph by workflow ID to inspect staged content changes and audit context before human review.

Instructions

List all nodes in a workflow graph

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": {
      "workflowId": "<workflowId>"
    },
    "name": "listWorkflowNodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
workflowIdYesWorkflow ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'List' implies a read-only, non-destructive operation and 'all' implies completeness (no filtering/pagination), but it says nothing about ordering, pagination, behavior for an invalid or missing workflowId, whether nested subgraph nodes are included, or what fields a node carries.

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 front-loaded sentence with zero filler. It is efficient, but the brevity comes at the cost of the routing and return-shape details an agent would want.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with a fully described schema and no output schema, this is minimally adequate: the agent knows what it retrieves. However, because no output schema exists, the description should say what a node record contains and how it differs from getWorkflow's output, which it does not.

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

Parameters3/5

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

Schema description coverage is 100% and there is a single required workflowId parameter, so the schema already documents the input. The description adds no format hints or constraints beyond what the schema provides, so the baseline of 3 applies.

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?

Names a specific verb and resource: list all nodes belonging to a workflow graph. An agent can tell what it retrieves, but the description never distinguishes it from siblings such as getWorkflow, which plausibly also returns node data, or from listWorkflows at the graph level.

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?

There is no when-to-use guidance, no mention of when to prefer getWorkflow or getNodeRuns instead, and no stated prerequisites beyond the required workflowId shown in the schema. The agent must infer selection purely from the tool name.

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