Skip to main content
Glama

Connect ClawCall call events

connect_webhook
Destructive

Send this account's call events (call.started for inbound calls, call.completed for every call) to an agent's own webhook trigger, such as a Grok Bot routine, then send a test event and return its result. get_calling_guide topic webhooks explains the setup. The user copies the trigger URL and key from their agent app and pastes them to you. Saving sets Authorization as the only custom header, and ClawCall emails the account owner whenever events start going to a new URL. If the account already sends events elsewhere, this fails with the current destination unless replace is true; confirm with the user first. Calling it again with the same URL and key re-tests the connection.

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": {
      "url": "<url>",
      "authorization": "<authorization>"
    },
    "name": "connect_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe agent's webhook trigger URL, exactly as the user copied it.
replaceNoTrue replaces an existing endpoint on a different URL. Ask the user first.
authorizationYesThe trigger's key exactly as the user pasted it in chat. A bare key is sent as "Bearer <key>"; a value with a scheme is sent as given. A masked placeholder such as [REDACTED] is refused.

Output Schema

NameRequiredDescriptionDefault
testYes
webhookYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag destructive/openWorld/non-idempotent; the description adds real behavior: Authorization is the only custom header set, the account owner is emailed when events start flowing to a new URL, and there is an explicit failure mode when a destination already exists. The email notification and header policy are side effects an agent could not infer from annotations alone.

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?

The primary action is front-loaded in the first clause and every remaining sentence carries a distinct fact (guide reference, paste workflow, header policy, email notice, replace failure, retest semantics). It is dense but not padded; only the guide reference could be trimmed.

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

Completeness5/5

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

For a destructive, externally-visible write tool, the description covers preconditions, side effects (owner email), header constraints, conflict handling via replace, and retest behavior, and an output schema covers the returned result. An agent has enough to call it safely without further discovery.

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%, so url, replace, and authorization are already documented including the Bearer-prefixing rule and the refusal of masked placeholders. The description reinforces that replace requires user confirmation and that the values arrive by paste, but adds little beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: send this account's call events (call.started, call.completed) to the agent's own webhook trigger, then fire a test event and return the result. No sibling tool touches webhooks, so it is cleanly separable from get_call_settings, update_call_settings, and the call-management tools.

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

Usage Guidelines5/5

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

It states the precondition (the user copies the trigger URL and key from their agent app and pastes them), the failure condition (an existing destination causes failure unless replace is true, and the user must confirm first), and the retest path (calling again with the same URL and key re-tests). It also points to get_calling_guide topic webhooks for setup.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.