Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_latest_conversation_messages

Retrieves recent messages for a conversation session to provide sufficient context without fetching detailed conversation data.

Instructions

Lists recent messages for one conversation. Use this when recent context is sufficient instead of retrieving detailed conversation data.

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_id": "<session_id>"
    },
    "name": "list_latest_conversation_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesThe conversation session identifier ('session_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does usefully disclose the key behavioral trait that results are a recent subset rather than the complete transcript, but leaves vague how many messages 'recent' means, the ordering, and whether truncation/pagination exists.

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 tight sentences with the action front-loaded and the usage condition second; no filler. The phrase 'detailed conversation data' is slightly vague but costs little.

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?

For a simple single-parameter read tool this covers the essentials, but with no output schema the description never indicates what a returned message contains and does not bound 'recent' in count or time. These gaps are modest given the tool's low complexity.

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?

Only one parameter and schema description coverage is 100%, so the schema already explains session_id fully. The description adds nothing about the identifier's semantics beyond what the schema states, making the baseline 3 appropriate.

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 ('Lists recent messages for one conversation') with a scope qualifier ('recent') that distinguishes it from full-detail retrieval. The differentiation from get_conversation is only implied via 'detailed conversation data' rather than named outright.

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?

Explicitly tells the agent to use this when recent context suffices and contrasts it with pulling detailed conversation data, which is a clear selection condition. It stops short of naming the alternative tool or stating when this tool is insufficient (e.g., auditing full history).

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