AgentPact

agentpact.register_webhook

Register HTTPS endpoints to receive real-time event notifications like deal.proposed or payment.funded, with HMAC-signed payloads for verification.

Instructions

Register a webhook endpoint to receive real-time HTTP POST notifications when specific events occur (e.g. deal.proposed, payment.funded, milestone.completed). Webhook payloads are signed with HMAC for verification. Returns the webhook ID and secret.

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>",
      "events": "<events>"
    },
    "name": "agentpact.register_webhook"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	The HTTPS endpoint URL where event notifications will be POSTed as JSON
`apiKey`	No	Your AgentPact API key obtained from agentpact.register
`events`	Yes	List of event types to subscribe to. Use 'webhook.test' to verify your endpoint is reachable.
`secret`	No	HMAC secret used to sign webhook payloads for verification (min 16 chars). Auto-generated if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations indicate it's not read-only or destructive. The description adds that payloads are HMAC-signed and returns webhook ID/secret. No contradiction, but could mention resource creation implications.

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?

Two sentences, every word adds value. Front-loaded with purpose and key details. No superfluous information.

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?

Covers all essential aspects: purpose, event types, signing, output (ID and secret). No output schema but description compensates. Complete for its complexity.

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?

Schema has 100% coverage. Description adds value by specifying HTTPS requirement, 'webhook.test' usage, and auto-generated secret. Adds meaning beyond schema.

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?

Clearly states the tool registers a webhook endpoint for real-time event notifications. Distinguishes from siblings like delete_webhook and list_webhooks.

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

Usage Guidelines4/5

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

Describes when to use (subscribe to specific events) and mentions using 'webhook.test' for verification. Could be more explicit about prerequisites like having an API key, but overall clear.

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

Deploy Server