Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

List Space agents

swarm_list_agent_participants
Read-onlyIdempotent

List this Space's participants before assignment or a mention. Returned executor_identity_id is for assignment, not a listing input. can_execute means eligibility, not presence or listening. Page with next_cursor; discover Spaces with swarm_list_spaces.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size; follow next_cursor for more.
cursorNoPrevious next_cursor; keep filters and order.
space_idNoSpace ID from swarm_list_spaces; omit if sole.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Previous next_cursor; same filters and order."New value: +"Previous next_cursor; keep filters and order."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size."New value: +"Page size; follow next_cursor for more."
    • changedInput schema / properties / space_id / description
      Previous value: -"Omit for a single approved Space."New value: +"Space ID from swarm_list_spaces; omit if sole."
  2. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Previous next_cursor; same filters and order."
    • addedInput schema / properties / limit / description
      Added value: +"Page size."
    • addedInput schema / properties / space_id / description
      Added value: +"Omit for a single approved Space."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description is free to add semantic constraints instead: pagination via next_cursor, and the caveat that can_execute means eligibility rather than presence/listening. It also clarifies that executor_identity_id is an assignment input, not a listing input — genuine context beyond annotations.

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?

Three very tight sentences, each carrying distinct information (purpose/trigger, field semantics, pagination and discovery pointer). It is telegraphic and relies on jargon (executor_identity_id, can_execute) without a brief gloss, but there is no filler.

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?

An output schema exists so return structure needn't be restated, yet the description still explains the two ambiguous response fields and how to paginate. Combined with the annotated safety profile, an agent has everything needed to call and interpret this tool correctly.

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 coverage is 100%, so limit, cursor and space_id are already documented, including the 'omit if sole' hint for space_id. The description adds no new syntax or format detail for the input parameters; its clarifications target response fields rather than inputs, so baseline 3 applies.

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+resource ('List this Space's participants') plus the triggering context ('before assignment or a mention'), and explicitly points to swarm_list_spaces for the adjacent capability. An agent can distinguish this from other list_* siblings without opening the schema.

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?

Gives a clear when-to-use frame (before assignment or mention) and names an alternative for a related need (swarm_list_spaces to discover Spaces). It does not explicitly say when *not* to call this or contrast with sibling list tools like swarm_get_space, but the routing guidance is concrete.

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

All Swarm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources