Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

search_people_profiles

Search CRM contacts by full name or email to locate a person record for profile lookup and follow-up.

Instructions

Searches CRM contacts by full name or email address. Use this to find a person record; use the search_conversations tool to find a 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": {
      "search_query": "<search_query>"
    },
    "name": "search_people_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_queryYesThe search query to filter people profiles by (eg. a name or email).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/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 disclosure burden. It never says whether matching is exact or partial, whether results are capped or paginated, or what a result contains; 'Searches' implies a read but that is only inferred.

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 zero filler, and the primary purpose precedes the sibling disambiguation. Nothing is repeated or padded.

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 one-parameter search tool this covers purpose and the main alternative, which may be enough to invoke it. But with no annotations and no output schema, the description should still say what results look like or how matching behaves, and that gap is left entirely open.

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% and the single parameter is already documented as 'a name or email'. The description restates the same accepted-value idea ('full name or email address') without adding matching semantics, so it does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Searches') applied to a specific resource ('CRM contacts') and names the searchable fields (full name, email). An agent can immediately tell this is a person-lookup tool rather than a conversation, page, or settings tool.

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 says 'Use this to find a person record' and routes the agent to search_conversations for the conversation case. It doesn't address the retrieval-by-identifier sibling (get_people_profile) or when to page through list_people_profiles_at_page instead, so a boundary is left unstated.

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