Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Test webhook

tailscale_test_webhook

Verify a webhook endpoint's configuration by sending a test event and confirming it receives events correctly.

Instructions

Send a test event to a webhook endpoint to verify it is configured correctly and receiving events.

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": {
      "webhookId": "<webhookId>"
    },
    "name": "tailscale_test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe webhook ID to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / webhookId / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that an actual event is dispatched to the external endpoint, consistent with openWorldHint, but says nothing about whether the call waits for delivery, whether repeated tests are rate-limited, or what a failed delivery means for the webhook's state.

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

Conciseness4/5

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

One well-formed sentence that leads with the action and closes with the purpose, with no padding. Slightly more could be earned by front-loading the verification intent or adding a clause on the expected response.

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

Completeness4/5

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

For a one-parameter, non-destructive diagnostic tool with annotations covering mutability and external reach, the description is nearly complete. The remaining gap is the return behavior — with no output schema, an agent cannot tell whether the result reports delivery success or just acknowledges dispatch.

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 coverage is 100% with a single documented parameter (webhookId, 'The webhook ID to test'), so the schema carries parameter meaning. The description adds no further detail such as where to obtain a webhook ID or whether the endpoint URL must already be registered; baseline 3 is appropriate.

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 names a specific verb+resource ('send a test event to a webhook endpoint') and states the outcome ('verify it is configured correctly and receiving events'), which separates it from siblings like create_webhook, get_webhook, and update_webhook. It does not explicitly name any sibling as an alternative, but the purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'verify it is configured correctly' — an agent can infer this is a post-setup diagnostic. There is no explicit when-to-use/when-not guidance, no statement on prerequisites (does the webhook need to be enabled first?), and no pointers to alternatives such as get_webhook for inspecting configuration.

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