Skip to main content
Glama

list_peers

Lists available Agent Router peers and their supported MCP, CLI, and API transports so agents can discover and route work to the appropriate tool.

Instructions

List Agent Router peers (Cursor, Claude, Codex, Slack, GitHub, Railway, Vercel, Supabase, Stripe, Linear) and their MCP/CLI/API transports.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It makes clear this is a read-style enumeration and reveals the return contents (peer names and transport types), which is the key behavioral fact, but it omits whether the call reaches the network, whether peers must be authenticated, or whether results are cached.

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 sentence, front-loaded with the verb and resource, with the enumerated peers and transports as the only elaboration. Nothing is padded or repeated.

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-parameter, read-only discovery tool with no output schema, the description is nearly sufficient because it names what is returned. The only material omission is its relationship to probe_peers and the call_* tools, which would help an agent pick correctly.

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 no parameter meaning for the description to add; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs, and it correctly implies no arguments are needed.

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 states a specific verb ('List') and resource ('Agent Router peers') and enumerates the concrete peers plus the transport kinds (MCP/CLI/API) that are returned, so an agent knows exactly what it gets back. It does not explicitly differentiate itself from 'probe_peers', leaving the list-vs-probe distinction implicit.

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?

There is no when-to-use statement, no mention of prerequisites, and no reference to any sibling such as probe_peers or call_api. An agent can infer that this is a discovery call, but the description does not say when listing is appropriate versus probing or routing.

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