Skip to main content
Glama

get_messages

Retrieve the message list for a specified conversation, with an optional limit on the number of messages returned. Use it to read chat history and check conversation status.

Instructions

获取指定会话的消息列表

Args: conversation_id: 会话 ID limit: 消息数量限制

Returns: 消息列表和状态

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "conversation_id": "<conversation_id>"
    },
    "name": "get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
conversation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations present, the description carries the full behavioral burden. It discloses only that it returns a message list and status; nothing about ordering, pagination behavior when limit is hit, permissions, or whether it marks messages read — all of which matter for a tool that shares a name-space with get_unread_messages.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The Args/Returns structure is readable and front-loaded with the purpose sentence. However, the Args block spends two lines restating parameter names with near-zero added meaning, so the brevity reflects under-specification as much as conciseness.

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?

For a read tool with two parameters, zero schema coverage, no annotations, and no output schema, the definition should explain ordering, pagination, and the shape of the returned 'status'. It does not, leaving the agent unable to predict results or handle a full message list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and does not. 'conversation_id: 会话 ID' merely restates the parameter name, and 'limit: 消息数量限制' adds little over the typed integer with a default of 50 already visible in the schema — no max value, no paging semantics, no format for the ID.

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 states a specific verb+resource: '获取指定会话的消息列表' (get the message list of a specified conversation). That is clearly distinguishable from send_message or get_conversations by resource, though it never explicitly contrasts with the close sibling get_unread_messages.

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 contains no when-to-use guidance and no exclusions. It does not tell the agent when to prefer this over get_unread_messages or how to page through a long conversation, so selection between these siblings is left entirely to inference.

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