Skip to main content
Glama

Rename a client or move to personal

dosai_update_contact
Destructive

Change a client's name, or move the card between clients and the owner's personal contacts (personal ones are not counted as clients). Editor or above.

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": {
      "workspace_id": "<workspace_id>",
      "contact_id": "<contact_id>"
    },
    "name": "dosai_update_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
scopeNo
contact_idYes
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed2 schema fields changed
    • removedInput schema / properties / contact_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / workspace_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this mutates state; the description usefully adds the permission requirement ('Editor or above') and the semantic consequence that a personal contact is no longer counted as a client. It stops short of explaining why the operation is destructive, whether a rename is reversible, or what happens to records tied to a contact when it moves between clients. That leaves a meaningful gap for a destructive write.

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 compact sentence that front-loads the primary action and follows with the secondary behavior and the permission note. No filler or redundant restatement of the title, though the trailing 'Editor or above' fragment is terse to the point of being slightly clipped.

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 four-parameter destructive mutation with no output schema and low schema coverage, the description covers the core intent and the permission gate but omits return behavior and side effects of moving a contact between scopes. An agent could call it correctly but cannot predict consequences or confirm success criteria.

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 coverage is only 25%, so the description carries more of the burden, and it does map the two concepts of rename (name) and scope movement. But it does not explain the scope enum values as parameters, the meaning of contact_id, whether name and scope can be supplied together or independently, or what the default scope is. The added meaning is partial rather than compensating for the coverage gap.

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 two concrete operations on a clearly identified resource: renaming a contact and moving a contact between client and personal scopes. An agent can distinguish this from read tools like dosai_get_contact, though it does not explicitly name any sibling or contrast with a pure move/rename tool. The parenthetical clarification that personal contacts are not counted as clients tightens the resource definition.

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

Usage Guidelines3/5

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

It supplies a real precondition, 'Editor or above', and disambiguates the personal-vs-client outcome, which helps an agent decide whether this is the right call. However, there is no explicit when-to-use versus alternative guidance (e.g., versus deal-moving or contact-lookup tools) and no statement of when not to use it or what to do if the contact is already in the target scope.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources