Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

set_conversation_email

Sets or updates the contact email address in a conversation’s metadata using the session ID, keeping customer contact details accurate.

Instructions

Sets the contact's email address in a conversation's metadata.

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>",
      "email": "<email>"
    },
    "name": "set_conversation_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe new email address for the conversation.
session_idYesThe conversation session identifier ('session_id' value).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about side effects. It does not say whether this writes to the conversation only or also mutates the contact/person record, whether the change is reversible, what permissions are required, or what happens on an invalid or duplicate email. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

The description is a single efficient sentence with no wasted words and the operation front-loaded. It is appropriately sized for the tool, though its brevity contributes to the missing behavioral detail rather than compensating for it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no annotations and no output schema, the description should explain side effects and the distinction from the profile-email sibling. It does neither, leaving the agent unable to predict whether setting the conversation email alters the person profile or how failures are surfaced.

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 both session_id and email are documented in the schema, establishing the baseline of 3. The description adds little beyond the schema and actually introduces mild tension by calling email 'the contact's email' while the schema calls it 'the new email address for the conversation.' No format, validation, or overwrite semantics are added.

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 states a specific verb and resource: setting a contact's email address within a conversation's metadata. An agent can understand the basic operation, though the phrasing 'in a conversation's metadata' is slightly ambiguous about whether the underlying person profile is affected. It does not name or distinguish itself from the sibling update_people_profile_email, which is the nearest conceptual neighbor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus update_people_profile_email or the sibling setters like set_conversation_full_name and set_conversation_phone. There are no stated prerequisites, situational conditions, or exclusions. The agent must infer usage entirely from the tool name.

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