Skip to main content
Glama

peers

Lists mesh sessions with address, kind, status, and rooms so you can inspect available agent connections; enable all to include long-offline sessions.

Instructions

List mesh sessions: address, kind, status, rooms, one per line. all: include long-offline ones.

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": "peers"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo

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 behavioral burden. It usefully discloses the line-oriented output shape and that 'all' includes long-offline sessions, but it does not state whether the operation is read-only, how results are ordered, or what 'long-offline' means.

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?

The description is two tight sentences with zero filler. The core purpose is front-loaded, followed immediately by the only parameter's effect.

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 simple one-parameter listing tool with no output schema or annotations, it covers the essential return fields and format plus the optional parameter behavior. It stops short of defining field meanings or exact output delimiters, but it is largely complete for its complexity.

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 schema coverage is 0% and there is one optional boolean parameter. The description compensates well by explaining that 'all' includes long-offline sessions, which is the key semantic an agent needs; the remaining ambiguity is what qualifies as 'long-offline'.

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: 'List mesh sessions', and names the fields returned. It is clear enough to distinguish this from a general 'rooms' or 'send' tool, but it does not explicitly contrast itself with any sibling.

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 description explains the effect of the 'all' parameter, but it gives no guidance on when to use this tool versus alternatives such as 'rooms' or 'history'. It also provides no exclusions or context about when a peer listing is appropriate.

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