Skip to main content
Glama

workflow_list

Saved workflows (ids go into run_start.workflow_id).

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": "workflow_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses almost nothing: it does not confirm the call is a side-effect-free read, does not describe the return shape (names? ids? ordering?), and says nothing about scoping or permissions. The one useful behavioral fact is the linkage to run_start.workflow_id, which is worth credit but is not enough for a tool with zero annotation coverage.

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 short parenthetical sentence with no filler, and the key fact (ids feed run_start.workflow_id) is placed immediately. The fragmentary phrasing is terse to the point of under-specification, but nothing is redundant.

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

Completeness2/5

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

With no output schema and no annotations, the description is the only source of truth about what comes back, and it never says whether the response is a list of ids, names, or full workflow objects. For a trivial zero-parameter list tool this is not dangerous, but an agent cannot tell what it will receive or how to pick an id from it.

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 no parameters, so the schema has nothing to explain and the baseline is 4. The description correctly adds no parameter detail and instead spends its words on the output-to-input relationship with run_start.workflow_id, which is the only semantic that matters here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Saved workflows" identifies the resource, and the parenthetical clarifies what the entries are used for, but the description never states the operation (list/retrieve) explicitly — that is only inferable from the tool name. It also does not distinguish itself from the sibling workflow_template_list, leaving the agent to guess at the difference between saved workflows and templates.

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?

The parenthetical "ids go into run_start.workflow_id" implies the intended use: fetch this list to obtain an id before starting a run. That is real, actionable guidance, but there is no explicit when-to-use statement, no exclusion of alternatives, and no mention of what to do if no workflows are returned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources