Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

list_latest_conversations

Lists recent workspace conversations to review activity. Use search_conversations to find conversations by message content or segments.

Instructions

Lists recent conversations for the workspace. Use the search_conversations tool when locating conversations by message content or segments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_latest_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/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 behavioral burden, and it does disclose two traits: results are workspace-scoped and returned in recency order. It omits how many conversations are returned, whether pagination or cursors exist, and whether permissions affect visibility — meaningful gaps for a list endpoint.

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?

Two short sentences, with the primary function stated first and the sibling routing second. No filler, no restatement of the tool name, and every clause carries information.

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 zero-parameter, no-output-schema list tool, the description covers what it returns conceptually and when to prefer the alternative. The remaining omission — result count, ordering guarantees, and pagination — is the only thing an agent would still need to guess.

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 tool takes zero parameters, so the baseline is 4; however, the description adds no information about the implicit behavior that a parameterless call implies (e.g., a default page size or server-side limit). That leaves it slightly below the zero-param baseline.

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 gives a specific verb and resource ("Lists recent conversations") scoped to the workspace, which is enough to distinguish it from content-based retrieval tools. It stops short of defining "latest" — no count, ordering, or time window — so the purpose is clear but not fully pinned down.

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?

It explicitly routes the agent to search_conversations for locating conversations by message content or segments, which is a genuine when-to-use alternative. It does not state any exclusions or conditions where this tool should be avoided (e.g., paging through older results).

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