LLM Bus

who_is_active

Retrieve recently active actors in a workspace or lane to verify the shared surface is clear before use.

Instructions

List actors seen within the liveness window (lane-scoped if lane is given). Check before touching a shared surface.

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

Input Schema

Name	Required	Description	Default
`lane`	No
`within_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. While it mentions lane-scoping and liveness, it does not disclose whether the operation is read-only, required permissions, or potential side effects. The behavioral traits are under-specified.

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 extremely concise with two short sentences that immediately state the purpose and a usage hint. Every word adds value, and it is front-loaded with the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, no annotations, and two optional parameters, the description lacks crucial context: what constitutes a 'liveness window', how 'within_seconds' modifies results, and what the output format is. It is incomplete for an agent to reliably invoke the tool without additional knowledge.

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 0%, so the description must explain parameters. It adds meaning to 'lane' by noting scoping, but fails to explain 'within_seconds' (its range, format, or effect). Only partial parameter semantics are conveyed.

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 verb 'List' and the resource 'actors seen within the liveness window'. It distinguishes the tool by specifying lane-scoping and hints at practical use, making it distinct from siblings like list_participants or whoami.

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 phrase 'Check before touching a shared surface' gives context for when to use the tool, but lacks explicit guidance on when not to use it or alternatives. No comparison with other sibling tools is provided.

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