Skip to main content
Glama

get_messages

Access your received messages with details of sender, content, and time. Optionally filter by status to find specific communications.

Instructions

查看收到的消息。返回消息列表含发送者、内容、时间。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo状态过滤(可选)

Implementation Reference

  • The handler case for 'get_messages' that parses args via GetMessagesSchema and calls client.getMessages(p.status).
    case 'get_messages': {
      const p = S.GetMessagesSchema.parse(args);
      result = await client.getMessages(p.status);
      break;
  • Zod schema for GetMessagesSchema, validates optional 'status' string parameter.
    export const GetMessagesSchema = z.object({
      status: z.string().optional(),
    });
  • src/index.ts:714-723 (registration)
    Registration of 'get_messages' tool with name, description, and inputSchema in the tools array.
    {
      name: 'get_messages',
      description: '查看收到的消息。返回消息列表含发送者、内容、时间。',
      inputSchema: {
        type: 'object' as const,
        properties: {
          status: { type: 'string', description: '状态过滤(可选)' },
        },
      },
    },
  • Registration of tool name 'get_messages' under the 'messaging' feature group.
    messaging: [
      'send_message', 'get_messages', 'list_conversations', 'get_conversation',
    ],
  • The low-level API client method getMessages that makes a GET request to /acap/v1/messages with optional status filter.
    async getMessages(status?: string) {
      const params = status ? `?status=${status}` : '';
      return this.request('GET', `/acap/v1/messages${params}`);
    }
Behavior2/5

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

With no annotations, the description must fully convey behavioral traits. It only states the basic purpose and return fields, omitting details like pagination, ordering, rate limits, or whether it returns all messages or only unread.

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 sentence with no wasted words, efficiently conveying the core purpose and return content.

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

Completeness3/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description provides adequate but not thorough context. It lacks scope clarification (e.g., all conversations vs. specific) and does not mention if messages are ordered or paginated.

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?

The input schema describes the 'status' parameter (status filter). Since schema coverage is 100%, the description does not need to add more, but it also does not enhance understanding beyond the schema.

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 '查看收到的消息' (View received messages) clearly identifies the verb and resource, distinguishing it from siblings like get_conversation and send_message. It also specifies return fields (sender, content, time).

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 is provided on when to use this tool vs alternatives such as get_conversation or other list tools. There is no mention of context, prerequisites, or exclusions.

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