Skip to main content
Glama

create_webhook

Send Trainzilla events to an https URL (Zapier/Make catch hook or the coach's server). Returns the signing secret ONCE — tell the coach to store it. Events: CLIENT_JOINED, PAYMENT_CONFIRMED, CHECKIN_SUBMITTED, PERSONAL_RECORD_HIT. (confirm-gated: previews until confirm: true)

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": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
eventsYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare non-read-only, non-destructive, closed-world, which the description is consistent with. The description adds genuinely useful behavior: the signing secret is returned only ONCE and must be stored, and calls without confirm:true return a preview instead of executing. It does not cover auth requirements, duplicate-URL behavior, or failure modes, so it is solid but not exhaustive.

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 dense sentences plus a short parenthetical, all front-loaded: purpose, critical secret-handling warning, event list, then the confirm gate. No sentence is filler.

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?

For a 3-parameter creation tool with no output schema, the description covers the essential risk (one-time secret), the invocation gate (confirm), and the event vocabulary. Missing only secondary details such as whether the secret can be rotated, what a preview response contains, or duplicate-URL handling.

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 only 33% (only confirm carries a schema description), so the description must compensate; it does explain the confirm preview gate and restates the allowed event values. The url parameter's https requirement and max length are left entirely to the schema pattern, and no format or validation guidance is added beyond what the schema encodes.

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 opens with a specific verb and resource ('Send Trainzilla events to an https URL') and enumerates the four event types, so the agent knows exactly what is created. It stops short of naming sibling tools such as send_test_webhook or set_webhook_active, so the boundary with those is left implicit.

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 concrete usage context (Zapier/Make catch hook or the coach's own server) and states the confirm-gated workflow, which tells the agent how to invoke it safely. It offers no explicit when-not guidance or pointer to alternatives for testing or managing existing webhooks.

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.