Skip to main content
Glama

List Specialist Agent Wings

list_agent_wings
Read-onlyIdempotent

List specialist multi-agent wings like architect, reviewer, QA, security, and ops with their active memory counts and recent handoffs to track agent activity and context flow.

Instructions

List specialist multi-agent wings (architect, reviewer, qa, security, ops), their active memory counts, and recent handoffs.

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

Input Schema

NameRequiredDescriptionDefault
namespaceNoOptional namespace filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the return payload (memory counts, handoffs), but leaves out behavioral details such as what 'recent' means, ordering, or any result cap.

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?

A single front-loaded sentence with no filler; every clause (wing types, memory counts, handoffs) conveys distinct information.

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?

For a one-optional-parameter, read-only listing tool with no output schema, the description is close to complete: it states the object, the variants, and the returned fields. Only the meaning of 'recent' and any result-size limits are left unstated.

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 description coverage is 100% for the single optional 'namespace' parameter, so the baseline is 3. The description never mentions namespace filtering, so it adds no meaning beyond the schema.

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 pairs a specific verb ('List') with a specific resource ('specialist multi-agent wings') and then enumerates the wing types (architect, reviewer, qa, security, ops), so an agent knows exactly what domain object is returned. It also names the payload (active memory counts, recent handoffs), which makes it unmistakable against siblings like stats, health, or handoff_to_agent.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The content does imply a discovery/inspection role (find a wing before calling handoff_to_agent), but the agent has to infer that routing itself.

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