Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

set_conversation_full_name

Set the contact's full name in a conversation's metadata using the session ID and new full name.

Instructions

Sets the contact's full name 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>",
      "full_name": "<full_name>"
    },
    "name": "set_conversation_full_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYesThe new full name 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 burden for a write operation. It does not disclose whether the existing full name is overwritten, what permissions are required, whether the change is reversible, or what happens if the session 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single clear sentence with the purpose front-loaded and no extraneous wording. Its brevity is appropriate, though it leaves useful behavioral detail unstated.

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 simple two-parameter setter, the description and schema together make the basic operation understandable. However, because annotations are absent and this is a mutation, the definition is incomplete regarding side effects, overwrite behavior, and failure conditions.

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 schema already documents both session_id and full_name, including the minimum length constraint. The description adds no additional parameter meaning beyond the field names already supplied by the schema, which is the expected 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?

The description states a specific verb and resource: it sets the contact's full name, scoped to a conversation's metadata. This distinguishes it from profile-level or email/phone setters in the sibling list, though it does not explicitly name an alternative.

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 explicit when-to-use guidance and does not clarify when to choose this tool over update_people_profile_full_name or other conversation metadata setters. Any usage context must be inferred from the tool name and description alone.

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