Skip to main content
Glama
crisp-plugin-mcp

crisp-plugin-mcp

by amitray007

update_people_profile_full_name

Updates a CRM contact's full name using a people ID or email address, so profile names stay accurate and current.

Instructions

Updates the full name of a specific CRM contact.

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": {
      "people_id_or_email": "<people_id_or_email>",
      "full_name": "<full_name>"
    },
    "name": "update_people_profile_full_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYesThe new full name for the CRM profile.
people_id_or_emailYesThe CRM profile people identifier or email address ('people_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 supplied, so the description carries the full behavioral burden and mostly fails to: it does not say whether the existing value is overwritten, what happens if people_id_or_email does not resolve to a contact, whether permissions or scopes are required, or what is returned. 'Updates ... new full name' implies replacement, but nothing about failure modes or side effects is disclosed.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity reflects an absence of content rather than tight editing of rich content.

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, fully schema-documented mutation tool with no output schema, the minimal description is close to adequate. However, with no annotations to cover safety and no statement of overwrite semantics or error behavior, an agent still lacks what it needs to invoke this confidently on production CRM data.

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%, with both parameters documented in the schema itself (identifier-or-email and the new name), so the baseline of 3 applies. The description adds no format, constraint, or edge-case detail beyond what the schema already states.

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?

States a specific verb ('Updates'), a specific field ('full name'), and a specific resource ('CRM contact'), so the agent can distinguish it from sibling field-updaters like update_people_profile_email and from set_conversation_full_name by target object. It stops short of explicitly routing the agent away from those siblings, so it is clear but not maximally differentiated.

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 when-to-use guidance, no prerequisite or permission context, and no mention of alternatives such as updating email or phone on the same profile. The agent must infer the usage entirely from the name and description noun.

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