Skip to main content
Glama
Sign In
MCP Bridge

MCP Bridge

by szeeshan896
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List delegable agents

list_agents

List AI agents this bridge can delegate to and check whether each is available now; unavailable entries include the reason, such as a missing CLI or stopped Ollama.

Instructions

List the AI agents this bridge can delegate to, and whether each one is usable right now. Check this before delegating: "available": false carries the reason, such as a CLI that is not installed or an Ollama that is not running.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does useful work: it discloses that availability is reported per agent and that "available": false carries a reason such as a missing CLI or a stopped Ollama. It's a read-only listing with no side effects, so the main remaining gap is the rest of the response shape.

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?

Two sentences, zero waste. The purpose comes first and the pre-delegation guidance follows, which is the right order for an agent scanning for whether to call it.

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?

With no output schema, the description supplies the one return detail that matters, the meaning of "available": false. A fuller field list would help, but the essentials for calling and interpreting this zero-param tool are present.

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?

Zero parameters, so the baseline of 4 applies. Nothing in the description is needed to disambiguate inputs.

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?

States a specific verb (List) and a precise resource (the AI agents this bridge can delegate to), and adds the per-agent usability status, which distinguishes it cleanly from ask_agent, start_task, and get_task.

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

Usage Guidelines4/5

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

"Check this before delegating" gives an explicit when-to-use condition tied to the delegation workflow. It doesn't name the sibling tools as alternatives, but there is little ambiguity here anyway.

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