RetailHardHat

Create Organization Webhook

create_organization_webhook

Create an organization webhook. Sends future selected event data to the reviewed HTTPS endpoint; signing secret is not exposed to AI. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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

Input Schema

Name	Required	Description	Default
`data`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The description adds critical contextual behavior not covered by annotations or schema, specifically stating that 'signing secret is not exposed to AI' (a security behavior) and detailing the mandatory 'business workflow approvals' (a workflow behavior). This is high-value information for a mutation tool.

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 two sentences are dense with information, covering the function, the security posture, and the necessary governance workflow. Every part of the description contributes meaningfully to the agent's understanding.

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

Completeness2/5

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

Given the complexity of the input schema (a massive list of event enums), the description is incomplete. It states data is selected but gives no guidance on *how* to select appropriate events or the expected format of the webhook payload beyond a URI.

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?

Since schema description coverage is 0%, the description provides only high-level clues about the parameters (e.g., 'reviewed HTTPS endpoint,' 'selected event data'). It does not clarify the purpose of the 'name' or explain how to select relevant events from the large enum list.

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 clearly states the action ('Create an organization webhook') and the function (sends future event data). By specifying 'organization webhook,' it differentiates this tool from the multitude of general `create` tools available among the siblings.

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 provides clear guidance on the organizational governance surrounding this tool, mentioning that MCP approvals are configurable and business workflows always apply. This helps the agent understand the operational constraints before deciding to invoke the tool.

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

All RetailHardHat 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?