agentshield-mcp

register_webhook

Register a webhook to monitor smart contract changes and receive alerts on ownership transfers, proxy upgrades, liquidity removals, or risk changes. Requires an API key and HTTPS callback URL.

Instructions

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": {
      "contract": "<contract>",
      "callback_url": "<callback_url>",
      "api_key": "<api_key>"
    },
    "name": "register_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No		ethereum
`events`	No	Events: proxy_upgrade, ownership_transfer, liquidity_removal, risk_change
`api_key`	Yes	AgentShield Pro/Builder API key
`contract`	Yes	Contract address to watch
`callback_url`	Yes	HTTPS URL to receive alerts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful context: registration action, plan requirement, and the types of contract changes triggering alerts. However, it omits operational details like idempotency, response format, webhook lifecycle, or duplicate handling, which limits transparency.

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, front-loaded sentence with a clear verb and resource. Every word earns its place; there is no fluff or redundancy.

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?

Despite the lack of an output schema and annotations, the description adequately covers the core purpose and prerequisite for a registration tool. The schema enriches parameter understanding. It could mention the response or webhook lifecycle, but the description is sufficiently complete for basic usage.

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?

The input schema covers 80% of parameters with descriptions, meeting the high-coverage baseline of 3. The description adds context tying events to contract changes and the plan requirement to api_key, but it does not provide syntax or format details beyond the schema's own descriptions.

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 clearly states the verb 'Register' with the resource 'webhook' and specifies the exact purpose: receiving alerts for contract ownership, proxy, or risk changes. This differentiates it from sibling tools like monitor_wallet or scan_contract by focusing on webhook-based notifications.

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?

The description implies a use case (setting up proactive contract change alerts) but does not explicitly compare with alternatives like get_alerts or monitor_wallet. The plan requirement (Pro/Builder) is mentioned as a prerequisite, but there is no when-to-use vs. when-not-to-use guidance.

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