Skip to main content
Glama

get_messages

Read-only

Read TalkJS messages from a mentor conversation. Requires Authorization: Bearer. conversation_id is the hash from list_conversations. Newest first. Pass starting_after with a message id to page into older messages.

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
starting_afterNo
conversation_idYes

Output Schema

NameRequiredDescriptionDefault
kindNo
errorNo
messageNo
messagesNo
next_stepNo
conversation_idNo
next_starting_afterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: the Bearer auth requirement, newest-first ordering, and the direction of pagination (starting_after walks into older messages). Only the default page size and the shape of the boundary condition (what happens at the oldest message) are left out.

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?

Four short sentences, each carrying a distinct fact (scope, auth, ordering, paging), with the prerequisite and the identifier provenance up front. No filler or repetition of the annotations.

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

Completeness5/5

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

An output schema exists, so return values needn't be described; the description instead covers the things the schema cannot — auth, sort order, and paging direction. Combined with the annotations, an agent has everything needed to call this correctly apart from the unexplained limit parameter.

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?

Schema description coverage is 0%, so the description must compensate and it does so only partially: conversation_id and starting_after get real meaning, but 'limit' is never mentioned anywhere, leaving one of three parameters undocumented in both places. The two explained parameters are well specified, so this is decent rather than deficient.

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?

States a specific verb and resource ('Read TalkJS messages') and scopes it to 'a mentor conversation', which separates it cleanly from the write-side siblings like send_message. It stops short of naming the complementary sibling (e.g. send_application_message vs send_message) or stating what kinds of messages are excluded, so it is clear but not fully differentiated.

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

Usage Guidelines4/5

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

'conversation_id is the hash from list_conversations' tells the agent how to obtain the required input, and the closing sentence gives the exact paging recipe. What is missing is any when-not guidance (e.g. that this is read-only history and must not be used to post) or a note about which conversations are valid.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources