Skip to main content
Glama

List Workflows

sirv_list_workflows
Read-onlyIdempotent

Lists saved workflows with their IDs, names, descriptions, step counts, and step types so you can identify and inspect the right workflow.

Instructions

List the saved workflows that you can see: each one's id, name, description, step count and step types, such as removeBackground and upscale.

Use it to find a workflow, then sirv_get_workflow for its settings. MCP cannot run a workflow: it runs in Studio. To repeat a step here, call that step's own tool, such as sirv_remove_background. It takes no inputs.

Read-only.

Credits: free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety bar is met structurally. The description still adds real context beyond them: the 'that you can see' visibility scoping, the explicit inability to execute workflows from MCP, 'It takes no inputs', and the 'Credits: free' cost note. It stops short of describing result ordering or pagination, which keeps it off a 5.

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-loads what the tool returns, then follows with the routing rule and constraints; short declarative sentences with no filler. The 'Read-only. Credits: free.' fragments are compact and functional, though the piece runs slightly longer than a minimal list tool needs.

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?

No output schema exists, yet the description compensates by enumerating the returned fields (id, name, description, step count, step types). For a parameterless, annotation-rich list tool this covers everything an agent needs before calling.

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?

Zero parameters, which sets the baseline at 4. The description reinforces this with 'It takes no inputs', leaving no ambiguity about invocation shape.

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?

States a specific verb and resource ('List the saved workflows') and immediately enumerates what each entry contains (id, name, description, step count, step types). It also distinguishes itself from sirv_get_workflow, so an agent can separate the two without opening either 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?

Gives an explicit routing rule: use this to find a workflow, then call sirv_get_workflow for settings. It also sets the boundary that MCP cannot run a workflow and that repeating a step means calling that step's own tool, naming sirv_remove_background as an example — clear when-to-use plus when-not-to-use with alternatives.

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