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

wecom-crm-mcp

by andyleimc-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wecom_customer

Manage customer contacts in WeCom. Retrieve details, list followers, batch get info, and add remarks.

Instructions

客户管理 — actions: list_followers / list / get / batch_get / remark.

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

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided. Description only lists actions without disclosing behavioral traits such as side effects, permissions, rate limits, or mutability. For a tool with multiple actions, this is insufficient.

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

Conciseness3/5

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

Description is very short but lacks structure. It front-loads the actions list but omits important sections. Could be more precise while remaining concise.

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

Completeness2/5

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

Given 0% schema description coverage, the description should compensate but does not. It does not explain output schema or behavioral context for the actions. Incomplete for effective tool selection.

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

Parameters2/5

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

Schema description coverage is 0%. Description does not explain the 'action' parameter values or 'params' object beyond listing actions. The schema provides no defaults or enums, leaving the agent without parameter guidance.

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?

Description states tool is for customer management and lists specific actions (list_followers, list, get, batch_get, remark). This makes the purpose moderately clear, though it lacks detail and doesn't fully distinguish from sibling tools.

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?

No guidance on when to use this tool versus alternatives. Does not explain which action to use in which scenario or compare with sibling tools like wecom_tag or wecom_group_chat.

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