Skip to main content
Glama

list_crew

Lists AI agent crews with each station’s state, project, owner, machine, and recent activity; filter with mine to show only your own crews.

Instructions

The crews as Tares sees them: one row per station (orchestrator, reviewer, releaser, builders, helpers) with its state (working, idle, waiting, quiet, ended), the project it is on, when it last spoke, the stations it started, and how many earlier sessions played it. Each row names its crew, the machine the crew runs on and the person it belongs to: two crews can have stations of the same name. With mine only the caller's own crews are listed.

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

Input Schema

NameRequiredDescriptionDefault
mineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose meaningful traits: the row-per-station shape, the enumerated state vocabulary, and the caveat that two crews can share a station name. It does not state that the operation is non-destructive/read-only explicitly, nor anything about result size, pagination, or permissions for listing crews.

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

Conciseness3/5

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

The content is front-loaded and the row contents come first, which is good, but the phrasing is ornate ('as Tares sees them') and the identity sentence is convoluted. It is longer than needed for a zero-required-parameter list tool, though little is strictly redundant.

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?

An output schema exists, yet the description still maps the row fields, which is harmless context rather than a gap. For a simple filtered listing with one optional boolean, the only real omission is any note about volume or pagination of results.

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?

Schema description coverage is 0% for the single parameter, so the description must explain it, and it does: 'With `mine` only the caller's own crews are listed' makes the flag's effect and default behavior clear. There is no detail on edge cases (e.g., multi-crew membership scope), but the core semantics are covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('The crews ... one row per station') and enumerates the row contents (state, project, last spoken, stations started, prior sessions), so an agent knows exactly what it is listing. It does not, however, distinguish itself from sibling listing tools such as desk_list or list_people, leaving that differentiation to name inference.

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

Usage Guidelines2/5

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

The only usage-adjacent statement is the `mine` scoping rule, which is a parameter behavior rather than a when-to-use guideline. There is no mention of when this tool is preferred over the other list_* siblings, nor any exclusion or precondition.

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