Skip to main content
Glama
sfyyy

Claude Code DingTalk MCP Server

by sfyyy

dingtalk_configure

Configure DingTalk webhook settings to integrate Claude Code with DingTalk robot notifications for sending task alerts and messages to groups.

Instructions

Configure DingTalk webhook settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookYesDingTalk webhook URL with access token
secretNoOptional secret for signature verification
keywordsNoOptional keywords for security validation

Implementation Reference

  • The handler function that executes the dingtalk_configure tool. It creates a new DingTalkClient instance with the provided configuration (webhook, secret, keywords) and returns a success message.
    private async handleConfigure(config: DingTalkConfig) {
      this.dingTalkClient = new DingTalkClient(config);
      return {
        content: [
          {
            type: 'text',
            text: '✅ DingTalk client configured successfully',
          },
        ],
      };
    }
  • Input schema definition for the dingtalk_configure tool, specifying properties for webhook (required), secret, and keywords.
    inputSchema: {
      type: 'object',
      properties: {
        webhook: {
          type: 'string',
          description: 'DingTalk webhook URL with access token',
        },
        secret: {
          type: 'string',
          description: 'Optional secret for signature verification',
        },
        keywords: {
          type: 'array',
          items: { type: 'string' },
          description: 'Optional keywords for security validation',
        },
      },
      required: ['webhook'],
    },
  • src/index.ts:62-84 (registration)
    Registration of the dingtalk_configure tool in the ListTools response, including name, description, and input schema.
    {
      name: 'dingtalk_configure',
      description: 'Configure DingTalk webhook settings',
      inputSchema: {
        type: 'object',
        properties: {
          webhook: {
            type: 'string',
            description: 'DingTalk webhook URL with access token',
          },
          secret: {
            type: 'string',
            description: 'Optional secret for signature verification',
          },
          keywords: {
            type: 'array',
            items: { type: 'string' },
            description: 'Optional keywords for security validation',
          },
        },
        required: ['webhook'],
      },
    },
  • src/index.ts:206-207 (registration)
    Switch case in CallToolRequestSchema handler that routes dingtalk_configure calls to the handleConfigure method.
    case 'dingtalk_configure':
      return await this.handleConfigure(args as unknown as DingTalkConfig);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'configure' which implies a write/mutation operation, but doesn't specify whether this is a one-time setup, overwrites existing settings, requires authentication, or has side effects like rate limits. This is a significant gap for a tool that likely modifies system state.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the complexity of a configuration tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., idempotency, permissions), expected outcomes, or error handling, which are crucial for an agent to use it correctly in context with sibling notification tools.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters (webhook, secret, keywords) with their types and optionality. The description adds no additional meaning beyond what the schema provides, such as example values or usage context, meeting the baseline for high coverage.

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?

The description clearly states the action ('configure') and resource ('DingTalk webhook settings'), making the purpose understandable. However, it doesn't differentiate this configuration tool from the sibling notification tools (dingtalk_notify_session_end, dingtalk_send_link, etc.), which would require a 5.

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. It doesn't mention prerequisites (e.g., needing a DingTalk account), exclusions, or how it relates to the sibling tools for sending notifications, leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sfyyy/claude-code-dingtalk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server