Skip to main content
Glama

read_messages

Retrieve messages from a conversation to view past communication and context. Use this tool to access message history for analysis or reference.

Instructions

Read messages from a conversation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:37-37 (registration)
    The 'read_messages' tool is registered in a TOOLS array on line 37 with description 'Read messages from a conversation'. It is part of a list of tools that are iterated over and registered via server.tool() at line 107.
    ["read_messages", "Read messages from a conversation"],
  • The tool schema is empty ({}) meaning no input parameters are defined. The handler simply returns a stub message.
    server.tool(name, desc, {}, async () => ({
  • The handler is an async arrow function that returns a stub response. This is a minimal MCP stub for Glama inspection; the real implementation is in a native binary.
    server.tool(name, desc, {}, async () => ({
      content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
    }));
Behavior1/5

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

No annotations and the description provides no behavioral details (e.g., whether reading marks messages, pagination limits, or ordering). The agent gets no insight into side effects or constraints.

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

Conciseness2/5

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

Extremely short but missing critical information. Conciseness should not sacrifice completeness; this is under-specified.

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

Completeness1/5

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

Given many similarly named sibling tools, the description is insufficient. No output schema, no explanation of conversation selection, and no differentiation from platform-specific message readers.

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 schema has zero parameters and 100% coverage. The description adds nothing beyond the schema, but since schema already documents all (0) parameters, baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Read messages from a conversation' but fails to specify which messaging service (e.g., iMessage, Slack, WhatsApp). It does not differentiate from sibling tools like slack_read_channel_messages or whatsapp_read_messages.

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

Usage Guidelines1/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 over alternative message reading tools. No prerequisites or context provided.

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/lanchuske/local-mcp-releases'

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