LLM Bus

list_participants

List all participants in the project roster with their name, kind, lane, admin status, and token activity. Use this to check for duplicates before provisioning a new admin.

Instructions

List every participant granted into THIS project (the roster): name, kind, lane, admin flag, and whether their token is active. Use before admin_provision to avoid creating a duplicate.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations provided, the description alone must convey behavioral traits. It discloses the data fields returned and implicitly indicates a read-only operation by describing the output as a roster listing. However, it does not mention potential performance characteristics, rate limits, or permissions required, which would be beneficial for a more complete transparency.

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 consists of two concise sentences: the first states the purpose and output fields, the second provides a usage tip. No superfluous words, and the information is front-loaded.

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?

Given the tool has no parameters and no output schema, the description adequately explains what the tool does and returns, and suggests a specific use case. It could be more complete by clarifying that it lists all participants without pagination or ordering, but overall it's sufficient for a simple list operation.

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 input schema has zero parameters, so schema description coverage is 100%. The description does not need to add parameter details. The baseline for 0 parameters is 4, and the description meets that standard.

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 action 'List' and the resource 'participants granted into THIS project (the roster)', and enumerates the fields returned (name, kind, lane, admin flag, token active). It distinguishes itself from sibling tools like admin_provision, admin_revoke, etc., by focusing on a read-only listing of participants.

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?

The description explicitly states when to use this tool: 'Use before admin_provision to avoid creating a duplicate.' This provides clear guidance on the workflow context and gives a specific alternative action to avoid.

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