mcp-dingding-bot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DINGTALK_BOT_SECRET | No | Your dingding group robot signature secret (for robots with signature verification enabled) | |
| DINGTALK_BOT_ACCESS_TOKEN | Yes | Your dingding group robot access token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_text_messageC | Send a plain text message |
| send_markdown_messageC | Send a markdown message |
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 2 tools
The two tools have clearly distinct purposes: one sends markdown-formatted messages, and the other sends plain text messages. While both involve sending messages, the format distinction is explicit and unlikely to cause confusion, though they could be seen as overlapping in the broader 'send message' function.
Both tool names follow a consistent verb_noun pattern with 'send_' prefix and descriptive suffixes ('markdown_message', 'text_message'). The naming is predictable and adheres to a clear convention throughout the set.
With only 2 tools, the server feels thin for a bot that might handle more messaging operations (e.g., sending images, files, or managing conversations). This minimal set limits functionality and suggests an incomplete surface for a typical bot domain.
The tool set is severely incomplete for a Dingding bot domain. It only covers sending two message types, missing essential operations like receiving messages, managing users or groups, handling events, or supporting other media formats, which will likely cause agent failures in broader use cases.