Skip to main content
Glama

test_webhook_connection

Verify webhook connectivity between Claude Desktop and Make.com to ensure reliable automation scenario execution.

Instructions

测试与Make.com webhook的连接

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'test_webhook_connection' tool. It sends a test POST request to the configured Make.com webhook URL and returns a formatted response indicating success or failure.
    private async testWebhookConnection() {
      if (!this.makeWebhookUrl) {
        return {
          content: [
            {
              type: 'text',
              text: '❌ Webhook URL未配置\n请在.env文件中设置MAKE_WEBHOOK_URL'
            }
          ]
        };
      }
    
      try {
        const testPayload = {
          action: 'test_connection',
          data: { test: true },
          timestamp: new Date().toISOString(),
          source: 'claude-mcp-test'
        };
    
        const response = await axios.post(this.makeWebhookUrl, testPayload, {
          headers: {
            'Content-Type': 'application/json'
          },
          timeout: 10000
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `✅ Webhook连接测试成功\n` +
                    `响应状态: ${response.status}\n` +
                    `响应时间: ${new Date().toISOString()}\n` +
                    `Make.com scenario可以正常接收数据`
            }
          ]
        };
      } catch (error) {
        if (axios.isAxiosError(error)) {
          return {
            content: [
              {
                type: 'text',
                text: `❌ Webhook连接测试失败\n` +
                      `错误: ${error.response?.status} - ${error.response?.statusText}\n` +
                      `请检查:\n` +
                      `1. Webhook URL是否正确\n` +
                      `2. Make.com scenario是否已启用\n` +
                      `3. 网络连接是否正常`
              }
            ]
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `❌ 连接测试失败: ${error instanceof Error ? error.message : '未知错误'}`
            }
          ]
        };
      }
    }
  • src/server.ts:76-84 (registration)
    Registers the 'test_webhook_connection' tool in the ListTools response, including its name, description, and input schema (which requires no parameters).
    {
      name: 'test_webhook_connection',
      description: '测试与Make.com webhook的连接',
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false
      }
    }
  • src/server.ts:99-100 (registration)
    Dispatches calls to the 'test_webhook_connection' handler in the CallToolRequestHandler switch statement.
    case 'test_webhook_connection':
      return await this.testWebhookConnection();
  • Defines the input schema for the tool, which accepts an empty object with no required properties.
    inputSchema: {
      type: 'object',
      properties: {},
      additionalProperties: false
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the purpose without detailing what the tool actually does (e.g., sends a test request, verifies endpoints, returns status codes) or any behavioral traits like error handling, side effects, or output format. This leaves the agent guessing about the tool's operation.

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 in Chinese that directly states the tool's purpose without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success/failure status, error messages) or how it behaves, which is crucial for a connection-testing tool. With sibling tools and no structured data to fill gaps, the description should provide more context about the tool's operation and results.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since the schema fully covers the lack of parameters, and the description doesn't need to compensate.

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 states the tool's purpose as '测试与Make.com webhook的连接' (Test connection with Make.com webhook), which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like get_scenario_status or trigger_make_scenario, leaving ambiguity about when to use this specific connection test versus other webhook-related operations.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, such as whether this should be used before configuring webhooks or as a diagnostic tool. With sibling tools present, this lack of differentiation is a significant gap.

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/Joseph19820124/make-mcp-integration-playbook'

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