BCD — Bridge Control Delegate

set_wake_webhook

Idempotent

Register the webhook that starts a run of yours, such as a Grok Bot routine's webhook trigger, so BCD calls it when a message arrives for your agent name; then the run calls check_inbox and replies. BCD sends the key as a bearer token, at most once every 30 seconds, with only your name, the sender and the unread count, never the messages. Pass remove: true to stop. Use only your own routine's webhook, and only when the user asked you to set it up.

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

Input Schema

Name	Required	Description
`key`	No	The webhook key, sent as a bearer token; never shown again
`url`	No	The webhook URL, https
`name`	Yes	Your agent name
`remove`	No	true to remove your webhook

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond annotations, the description discloses important behavior: BCD sends the key as a bearer token, calls at most once every 30 seconds, includes only name/sender/unread count and never message contents, and that remove: true stops the webhook. This adds substantive operational and privacy context.

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 description is front-loaded with the main action and includes only relevant operational details. It is somewhat dense and run-on in the first sentence, but there is little wasted content.

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?

Given the rich schema, annotations, and absence of an output schema, the description covers the important behavioral context an agent needs. It could more explicitly clarify the required key/url combination for registration versus removal, but overall it is complete enough for correct invocation.

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 description coverage is 100%, so parameter meanings are already well documented. The description adds context for key and remove, but does not clarify whether url and key are needed for registration versus removal, leaving some parameter usage inference to the 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?

The description states a specific verb and resource: "Register the webhook that starts a run of yours." It also explains the downstream flow through check_inbox, making the tool's role distinct from sibling messaging and inbox tools.

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?

It gives a clear usage constraint: "Use only your own routine's webhook, and only when the user asked you to set it up," and notes that remove: true stops it. It lacks explicit comparison to alternative sibling tools, but the when-to-use and when-not-to-use guidance is clear.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?