Skip to main content
Glama
Sign In
wecom-crm-mcp

wecom-crm-mcp

by andyleimc-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wecom_transfer_resigned

Transfer customers and group chats from resigned employees. Manage unassigned lists, execute transfers, and retrieve transfer results.

Instructions

离职继承 — actions: get_unassigned_list / resigned_transfer_customer / resigned_transfer_result / groupchat_transfer.

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_transfer_resigned"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior, but it only lists action names without explaining side effects, permissions, or any behavioral traits, offering minimal transparency.

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 short, but it is not concise in a helpful way; it omits essential information and lacks a clear structure, making it under-specified.

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, optional params, output schema exists), the description is severely incomplete, failing to explain return values, action behavior, or parameter details.

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?

Schema coverage is 0%, and the description does not explain the 'params' object or how to use it with each action, leaving parameter semantics completely undefined.

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 includes the Chinese phrase '离职继承' and lists actions, giving a hint about resigned employee transfer, but does not explicitly state the tool's overall purpose in natural language.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus siblings, nor any context for choosing among the listed actions, leaving the agent without usage direction.

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

Deploy Server

Other Tools