wecom-crm-mcp

wecom_contact_way

Manage WeCom contact methods and group chat join ways. Perform actions like add, update, delete, list, get, close temp chat, and manage group chat join ways.

Instructions

联系我 / 加入群聊 — actions: add / get / list / update / del / close_temp_chat / groupchat_*_join_way.

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": {
      "action": "<action>"
    },
    "name": "wecom_contact_way"
  }
}

Input Schema

Name	Required	Description	Default
`action`	Yes
`params`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 5, 2026

TDQS

C2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions destructive actions like 'del' and 'close_temp_chat' but does not explain side effects, permissions, or reversibility. The description fails to provide adequate behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is extremely concise but lacks structure and completeness. It is a single line that lists actions without explanation, making it under-specified rather than effectively concise.

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

Completeness1/5

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

Given the tool's complexity (multiple actions) and minimal schema, the description is severely incomplete. It does not explain return values, action-specific details, or how to construct the 'params' object. The agent cannot reliably use this tool based solely on the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% schema description coverage. The description lists possible actions but does not explain what the 'params' object should contain for each action. The agent has no semantic information about the parameters beyond their names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists possible actions like add, get, list, update, del, close_temp_chat, and groupchat_*_join_way, which implies the tool manages contact ways and group chat join ways. However, it lacks a clear, concise statement of the tool's overall purpose and does not distinguish it from sibling tools like wecom_group_chat.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or scenarios where another sibling tool would be more appropriate.

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

Deploy Server