Skip to main content
Glama
kimi-sessions
by KekcuHa

Read Kimi Code session messages

GetMessages

Read recent text messages from a session, newest first, to collect another session's replies without marking them as read.

Instructions

Read recent text messages from a session, newest first. Useful for collecting another session's reply; it does not mark messages as read.

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": {
      "session": "<session>"
    },
    "name": "GetMessages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of messages
sessionYesExact session name or session_ ID
after_idNoReturn messages newer than this message ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.3

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one important trait: reading "does not mark messages as read", a real side-effect concern for messaging APIs. It omits other behavioral context such as permission requirements, whether results are capped by the tool itself, or how paging interacts with the newest-first ordering.

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

Conciseness4/5

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

Two short sentences with no filler, front-loading the core read operation before the use case and the read-state caveat. Efficient, though slightly more structure could separate the use case from the caveat.

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 three-parameter read tool with no output schema and no annotations, this covers purpose, ordering, and a key non-effect. Only the returned message shape and any access constraints are left implicit, which is a minor gap.

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 100%, so all three parameters are already documented, which sets the baseline at 3. The description adds the return ordering ("newest first"), which is genuinely new meaning not in the schema, but gives no further hints on limit or after_id usage.

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?

Names a specific verb and resource: "Read recent text messages from a session", plus the ordering ("newest first"). It implicitly contrasts with SendMessage, but never names a sibling or states the distinction explicitly, so it stops short of a 5.

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?

Provides one concrete use case ("collecting another session's reply"), which implies when to reach for it. It does not say when not to use it, how it relates to SendMessage/ListAgents, or what happens with sessions you cannot access.

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

Deploy Server

Other Tools