Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

search_conversations

Locate workspace conversations by searching message content or conversation segments, so you can find specific discussions instead of sorting by recency.

Instructions

Searches workspace conversations by message content or conversation segments. Use this when locating a conversation by content or segment rather than recency.

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": {
      "search_query": "<search_query>"
    },
    "name": "search_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_inNoWhat to search in (use 'text' to search in messages).text
search_queryYesThe search query to find matching conversations (searches in metas and messages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior2/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, and it discloses very little beyond the verb: no result limits, pagination, ordering, permissions, or whether the search is read-only. For a search tool with an enum-driven scope parameter, the behavioral surface is largely unexplained.

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, zero filler, with the capability stated first and the usage condition second. Every sentence earns its place.

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?

The tool is simple (2 params, no nesting, no output schema), and the description covers what it searches and when to choose it. It leaves the agent guessing about result shape and volume, which matters for a search tool where a caller needs to know whether it returns IDs, messages, or paginated pages.

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 the baseline is 3. The description's mention of 'message content or conversation segments' loosely maps to the search_in enum values, but it does not clarify what 'segments' actually contains or how search_query matches, so it adds little beyond the schema.

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?

Description gives a specific verb+resource ('Searches workspace conversations') plus two search facets ('message content or conversation segments'), which is more precise than a bare name restatement. It implicitly separates itself from recency-based listing siblings via the 'rather than recency' clause, though no sibling is named.

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 states the selecting condition: use it when locating a conversation by content or segment instead of recency, which routes the agent away from list_latest_conversations-style tools. It stops short of naming alternatives or stating when not to use it (e.g., when an exact conversation ID is already known, get_conversation would be better).

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