Skip to main content
Glama

mavis_comm_peers

List all reachable (active) sessions in the Mavis network, optionally filtered by agent name or session ID, to discover available peers for communication.

Instructions

List all reachable (active) sessions in the Mavis network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoFilter by agent name (e.g. mavis, coder, general)
sessionIdNoSession ID to query peers for (defaults to __MAVIS_PARENT_SESSION_ID)

Implementation Reference

  • The mavis_comm_peers tool is executed via the generic runTool function (line 77). This spec object defines the tool's buildArgs, which constructs the CLI args ['communication', 'peers'] and resolves sessionId from input or env var. No custom execFn is set, so it uses execMavisJSON (line 84) to call the Mavis binary.
      }
    },
  • Input schema for mavis_comm_peers: optional 'agent' (string) and optional 'sessionId' (string) fields defined using zod.
    inputSchema: z.object({
      agent: z.string().optional().describe('Filter by agent name (e.g. mavis, coder, general)'),
      sessionId: z.string().optional().describe('Session ID to query peers for (defaults to __MAVIS_PARENT_SESSION_ID)')
    }),
  • src/index.js:211-211 (registration)
    The tool spec is registered in the 'tools' array (line 98) under the name 'mavis_comm_peers'. The MavisServer constructor (line 484) builds a toolMap from this array and registers handlers via ListToolsRequestSchema (line 486) and CallToolRequestSchema (line 494).
    name: 'mavis_comm_peers',
Behavior2/5

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

No annotations provided, so description carries full burden. It only states a read-like operation but does not disclose any behavioral traits such as required permissions, rate limits, or what 'reachable' entails.

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?

Single sentence, no redundancy, gets straight to the point. Every word contributes to the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Simple tool with no output schema. Description does not indicate the return format (e.g., array of session IDs or objects). Missing critical information about what the agent will receive, leaving ambiguity.

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 coverage is 100% with both parameters described in the input schema. Description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states the verb 'List', the resource 'reachable (active) sessions', and the scope 'Mavis network'. It distinguishes from sibling 'mavis_session_list' by specifying 'reachable (active)' which implies a subset of all sessions.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, no when-not-to-use instructions. It does not explain how 'reachable' is defined or when to prefer this over mavis_session_list.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cunning-Kang/mavis-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server