Skip to main content
Glama
Sign In
SoloFlow

SoloFlow

by halexzd686-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Agents

soloflow_list_agents

List all configured agents with their names, descriptions, bound skills, and personality settings, so you can review available workflow components at a glance.

Instructions

列出所有可用的 SoloFlow Agent 智能体。返回 Agent 名称、描述、绑定的 Skill、性格设定。

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_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It describes the listing action and return fields, but does not explicitly state that the operation is read-only, non-destructive, or what side effects (if any) may occur. The behavior is implied by 'list', but not fully disclosed.

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, clear, front-loaded sentence that directly states the action and returned data. Every word earns its place, with no unnecessary details or repetition.

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?

The tool is simple (no params, no output schema) and the description adequately covers what is returned (agent name, description, bound Skill, personality). It does not explain the list format or whether agents are paginated, but for a basic list tool this is acceptable.

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, so the description does not need to explain parameter semantics. According to the rubric, a baseline of 4 is appropriate when there are no parameters, and the description adds no harmful ambiguity.

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 the tool lists all available SoloFlow Agent agents and specifies the returned fields (name, description, bound Skill, personality settings). This distinguishes it from sibling tools like soloflow_list_skills, which list skills instead of agents.

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 description implies the tool is used to discover available agents, but it does not explicitly state when to use this tool vs alternatives (e.g., soloflow_list_skills for skills). No exclusionary guidance is provided, though the resource type (Agents) is clear enough.

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