Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

get_conversation

Retrieve detailed data and metadata for a single conversation by session ID. Fetches the full conversation record so you can inspect its details.

Instructions

Returns detailed data and metadata for one conversation. This response may be verbose; use the list_latest_conversation_messages tool if you need messages from that conversation.

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": "get_conversation"
  }
}

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.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral trait — the response may be verbose — and steers to a cheaper alternative, but it never states permissions, side effects, or pagination/size limits; 'Returns' implies read-only only by inference.

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 sentences, zero waste, and the core purpose is front-loaded before the alternative-route hint. Every sentence earns its place.

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 one-parameter getter with no output schema, the description covers what it returns in broad terms, warns about verbosity, and redirects for messages. The main residual gap is that the shape of the returned 'data and metadata' is unspecified, which matters more here because no output schema exists to compensate.

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?

Single required parameter with 100% schema description coverage, so the schema already explains session_id. The description adds no meaning about the identifier's format or origin, which is acceptable at this coverage level but is pure 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?

States a specific verb and resource: 'Returns detailed data and metadata for one conversation.' It also names a sibling (list_latest_conversation_messages) and the condition that separates them, so an agent can distinguish the two without opening either schema. The only softness is 'detailed data and metadata,' which does not say what fields come back.

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?

Gives a clear routing rule: if you need messages from that conversation, use list_latest_conversation_messages instead, implying this tool is for the conversation record itself. It does not cover other plausible alternatives (e.g. list_people_conversations or list_latest_conversations), so the exclusion set is partial rather than exhaustive.

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