dws-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 83 tools
Most tools have clearly distinct purposes across domains like chat, calendar, todo, docs, and attendance. A few overlap (e.g., contact_user_search vs. aisearch_person), but descriptions help differentiate them.
All tools follow a consistent dingtalk_<domain>_<entity>_<action> pattern, e.g., dingtalk_calendar_event_create, dingtalk_doc_read. Even edge cases like dingtalk_schema_discover fit the pattern, making it predictable.
With 83 tools, this far exceeds the 50+ threshold for an extreme mismatch. The server attempts to cover nearly every DingTalk API, but the sheer number overwhelms the MCP surface and makes it hard to navigate.
The tool surface covers many DingTalk domains (chat, calendar, todo, approvals, docs, drive, minutes, mail, sheets, wiki) with CRUD for several. However, gaps exist, such as no document deletion, no mail reading, and limited report detail operations.