Skip to main content
Glama

list_conversations

List all conversations with counterparty agent information and the last message for each conversation.

Instructions

列出消息会话。返回会话列表含对方 Agent 信息和最后消息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of list_conversations: makes a GET request to /acap/v1/messages/conversations via the client's request method.
    async listConversations() {
      return this.request('GET', '/acap/v1/messages/conversations');
    }
  • src/index.ts:725-728 (registration)
    Tool registration entry defining name, description, and empty inputSchema for the 'list_conversations' tool.
      name: 'list_conversations',
      description: '列出消息会话。返回会话列表含对方 Agent 信息和最后消息。',
      inputSchema: { type: 'object' as const, properties: {} },
    },
  • The handler switch-case that calls client.listConversations() when 'list_conversations' is invoked.
    case 'list_conversations': {
      result = await client.listConversations();
      break;
  • Grouping of 'list_conversations' under the 'messaging' feature category in the feature-to-tools mapping.
    messaging: [
      'send_message', 'get_messages', 'list_conversations', 'get_conversation',
    ],
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses return content (agent info, last message) but lacks details on ordering, pagination, or limitations.

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, front-loaded with action, no wasted words.

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 0-parameter tool, the description covers basic behavior and output. However, it could be more complete by mentioning ordering or pagination.

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?

No parameters exist, so the description does not add parameter info. Baseline for 0 parameters is 4, which 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?

The description explicitly states the tool lists message conversations, including agent information and last message. It clearly distinguishes from siblings like get_conversation (singular) and get_messages.

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

Usage Guidelines3/5

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

The description implies usage for listing conversations but provides no explicit guidance on when to use it versus alternatives or when not to use it.

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/ggqshuai-hub/a2amarket-mcp-server'

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