Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by merlinh0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_agents

List every agent under control and report each one's current state—starting, working, idle, exited, or closed—so you can monitor parallel coding agents from a single conversation.

Instructions

List every agent under control with its state.

state: starting | working | idle (turn finished, waiting for you) | exited | closed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does add real value by enumerating the state machine (starting/working/idle/exited/closed) and clarifying that 'idle' means the turn finished and the agent awaits the caller, but it omits whether this is a pure read, whether it spans all sessions, and how many agents can be expected.

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?

Two short lines, front-loaded with the core action, with no filler. The state legend slightly overlaps what an output schema would normally express, but it adds interpretation ('waiting for you') rather than merely restating values.

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 zero-argument list tool with an output schema present, the description covers purpose and the meaning of each returned state, which is the main thing an agent must interpret. Minor gaps remain around scope ('under control' = which sessions?) and ordering.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The state legend, while not a parameter, usefully documents the shape of the returned values.

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?

States a specific verb and resource ('List every agent under control') plus the scope of the listing. It is clearly distinct from single-agent sibling get_agent by implication ('every agent'), but never names that sibling or explains the boundary explicitly.

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 'under control' hints at when this is appropriate, and the 'idle (turn finished, waiting for you)' gloss implies the listing tells you which agents are ready for input. There is no explicit when-to-use statement and no named alternative such as get_agent for a single agent or wait_for_agents for blocking.

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

Deploy Server

Other Tools