Skip to main content
Glama

list_conversations

Retrieve all active XMTP conversations to manage decentralized messaging interactions.

Instructions

List all active XMTP conversations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_conversations' tool. It checks if the XMTP client is connected, lists all conversations using client.conversations.list(), maps them to a simple object with id and createdAt, formats as JSON, and returns it wrapped in the MCP response format.
    private async listConversations() {
      if (!this.state.client) {
        throw new Error("XMTP client not connected. Use connect_xmtp tool first.");
      }
    
      try {
        const conversations = await this.state.client.conversations.list();
        
        const conversationList = conversations.map((conv) => {
          return {
            id: conv.id,
            createdAt: conv.createdAt?.toISOString(),
          }
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(conversationList, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to list conversations: ${error}`);
      }
    }
  • The input schema for the 'list_conversations' tool, which takes no parameters (empty properties).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • src/index.ts:169-176 (registration)
    The tool registration object defining the name, description, and input schema for 'list_conversations' within the tools array passed to setTools.
    {
      name: "list_conversations",
      description: "List all active XMTP conversations",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:223-224 (registration)
    The switch case in the tool request handler that dispatches calls to the 'list_conversations' handler function.
    case "list_conversations":
      return await this.listConversations();
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this lists 'active' conversations, implying a filter, but doesn't explain what 'active' means, whether this is a read-only operation, how results are returned (e.g., pagination), or any rate limits. This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'active' entails, the return format, or how this tool relates to siblings like 'get_messages'. For a tool with no structured behavioral data, more context is needed to be fully helpful.

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 has 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it correctly doesn't mention any parameters, earning a baseline high score for this dimension.

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 clearly states the verb ('List') and resource ('active XMTP conversations'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_messages' or 'stream_messages', which also deal with conversations/messages, so it doesn't reach the highest clarity level.

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 provides no guidance on when to use this tool versus alternatives like 'get_messages' or 'stream_messages'. It doesn't mention prerequisites (e.g., whether 'connect_xmtp' must be called first) or exclusions, leaving the agent to infer usage context.

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/kwaude/xmtp-mcp'

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