Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

listWorkflows

Retrieve workflow definitions for a project and optionally filter by site to inspect staged content approval paths before proposing changes.

Instructions

List workflow definitions for a project, optionally filtered to one site.

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": {
      "projectId": "<projectId>"
    },
    "name": "listWorkflows"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdNoOptional site ID filter
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it signals a read-only enumeration via "List" but says nothing about pagination, result limits, ordering, or whether unpublished/draft workflows are included. For a simple list operation this is a moderate gap rather than a critical one.

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 sentence with no filler, and the optional filter is placed after the core purpose so the primary action reads first. Nothing is redundant, though there is little structure to evaluate.

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?

For a two-parameter read-only listing tool with fully documented parameters and no output schema, the definition covers what the agent needs to invoke it. The main remaining gap is return-shape and pagination behavior, which is modest given the tool's simplicity.

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%, so both projectId and siteId are already documented. The description's "optionally filtered to one site" merely restates the siteId schema text and adds no format, default, or behavioral detail beyond it.

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 workflow definitions") plus the scoping unit ("for a project"), which cleanly separates it from the singular getWorkflow and from listWorkflowNodes. It does not explicitly reference any sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the enumeration call for workflows within a project. There is no statement of when to prefer it over listWorkflowNodes or getWorkflow, and no preconditions or exclusions are given.

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