Skip to main content
Glama
Sign In
SoloFlow

SoloFlow

by halexzd686-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Flows

soloflow_list_flows

List all available Flow workflows to view their names, versions, step counts, and descriptions. Use this to inspect existing workflows before running or managing them.

Instructions

列出所有可用的 SoloFlow Flow 工作流。返回 Flow 名称、版本、步骤数、描述。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It states the tool lists flows and returns specific fields, implying a read-only operation. However, it does not explicitly confirm safety, lack of side effects, or any limitations (e.g., pagination). For a simple list operation, this is adequate but not richly transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence in Chinese that states both the action and the output. It is front-loaded with the primary purpose and contains no filler or redundant details.

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?

For a zero-parameter listing tool with no output schema, the description fully covers the necessary context: it identifies the resource type, scope (all), and the fields returned. No additional context is needed for correct invocation.

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 has zero parameters, and schema coverage is 100%. The description does not need to explain parameters. The schema already shows an empty properties object, and the description's mention of return fields adds clarity without duplicating parameter info. Baseline for 0 params is 4.

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?

The description clearly states 'list all available SoloFlow Flow workflows' with a specific verb ('list') and resource ('Flow workflows'). It also enumerates the return fields (name, version, step count, description), which distinguishes it from sibling tools like soloflow_list_skills and soloflow_list_agents.

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

Usage Guidelines4/5

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

The description provides clear context: it returns all flows, so an agent knows when to use this tool (to enumerate available flows). It does not explicitly mention alternatives or exclusions, but the purpose inherently separates it from run/validate tools, so it meets the 'clear context' level.

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

Deploy Server

Other Tools