Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

set_conversation_phone

Sets the contact's phone number in a conversation's metadata using the session ID and an E.164-formatted phone number.

Instructions

Sets the contact's phone number 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>",
      "phone": "<phone>"
    },
    "name": "set_conversation_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesThe new phone number 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

B3.3/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 behavioral burden. It does disclose that the write is confined to conversation metadata (implying the contact's profile phone is untouched), which is genuinely useful, but says nothing about permission requirements, overwrite behavior, or what happens when the session or contact is missing.

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?

A single front-loaded sentence with no filler, and the scoping detail ('in a conversation's metadata') arrives in the same clause rather than being buried.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the essential what and where but omits failure modes, reversibility, and whether the phone is validated against or synced with the contact profile. Adequate but with clear gaps for a write operation.

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%, including an e164 format and regex constraint on phone and a description of session_id, so the schema already documents both parameters fully. The description adds no format, source, or validation context beyond what the schema states, making the baseline 3 appropriate.

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 names a specific verb and resource ('Sets the contact's phone number') and scopes it to conversation metadata, which implicitly separates it from siblings like set_conversation_email and set_conversation_full_name. It does not explicitly contrast itself with any sibling, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus the closely related update_people_profile_phone, nor any note about prerequisites or conditions for success. The agent must infer the conversation-vs-profile distinction entirely from the tool names.

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