Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create webhook

tribeunal_create_webhook

Register an HTTPS endpoint to receive signed Tribeunal case event notifications, returning a one-time signing secret for verifying deliveries.

Instructions

Register a URL that Tribeunal will POST your cases' events to. Events are owner-scoped: an endpoint receives events for cases YOU own, and, for a dispute you are a party to, dispute.opened, comment.created, evidence.marked, case.closed, appeal.filed and ruling.final (never votes or jury events). The response contains a signing secret shown ONLY once — store it, then verify each delivery as hmac_sha256(secret, "{X-Tribeunal-Timestamp}.{raw body}") against the hex in X-Tribeunal-Signature (format "v1="). Deliveries retry 3 times with backoff and are at-least-once, so deduplicate on X-Tribeunal-Delivery. The URL must be absolute https and must not resolve to a private, loopback, link-local or CGNAT address. An 11th endpoint answers 409 endpoint_limit (cap: 10 per account). Change events or pause delivery with tribeunal_update_webhook; the URL and secret cannot be changed — delete with tribeunal_delete_webhook and re-create instead. Returns {uuid, url, events, active, secret} — secret appears here and nowhere else.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute https URL to receive the signed POST deliveries; rejected (400 invalid_url / url_not_allowed) if it isn't https, carries embedded credentials, or resolves to a private, loopback, link-local, or CGNAT address.
eventsYesOne or more of case.opened, case.closed, vote.cast, vote.revoked, comment.created, evidence.marked, evidence.unmarked, jury.joined, ping, dispute.opened, appeal.filed, ruling.final; an unknown name answers 400 invalid_events. 'ping' fires only when the endpoint is pinged from the web dashboard or API — no MCP tool sends it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.0
    • changedInput schema / properties / events / description
      Previous value: -"One or more of case.opened, case.closed, vote.cast, vote.revoked, comment.created, evidence.marked, evidence.unmarked, jury.joined, ping; an unknown name answers 400 invalid_events. 'ping' fires only when the endpoint is pinged from the web dashboard or API — no MCP tool sends it."New value: +"One or more of case.opened, case.closed, vote.cast, vote.revoked, comment.created, evidence.marked, evidence.unmarked, jury.joined, ping, dispute.opened, appeal.filed, ruling.final; an unknown name answers 400 invalid_events. 'ping' fires only when the endpoint is pinged from the web dashboard or API — no MCP tool sends it."
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "case.opened",
-  "case.closed",
-  "vote.cast",
-  "vote.revoked",
-  "comment.created",
-  "evidence.marked",
-  "evidence.unmarked",
-  "jury.joined",
-  "ping"
-]New value: +[
+  "case.opened",
+  "case.closed",
+  "vote.cast",
+  "vote.revoked",
+  "comment.created",
+  "evidence.marked",
+  "evidence.unmarked",
+  "jury.joined",
+  "ping",
+  "dispute.opened",
+  "appeal.filed",
+  "ruling.final"
+]
  2. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / events / description
      Previous value: -"Events to subscribe to. One or more of: case.opened, case.closed, vote.cast, vote.revoked, comment.created, evidence.marked, evidence.unmarked, jury.joined, ping"New value: +"One or more of case.opened, case.closed, vote.cast, vote.revoked, comment.created, evidence.marked, evidence.unmarked, jury.joined, ping; an unknown name answers 400 invalid_events. 'ping' fires only when the endpoint is pinged from the web dashboard or API — no MCP tool sends it."
    • changedInput schema / properties / url / description
      Previous value: -"HTTPS URL that will receive the signed POST requests"New value: +"Absolute https URL to receive the signed POST deliveries; rejected (400 invalid_url / url_not_allowed) if it isn't https, carries embedded credentials, or resolves to a private, loopback, link-local, or CGNAT address."
  3. First observedv1.13.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations are thin (non-read-only, non-destructive, non-idempotent), and the description carries the full load: secret shown only once, HMAC verification formula and header format, 3 retries with backoff, at-least-once delivery requiring dedupe on X-Tribeunal-Delivery, SSRF-style URL restrictions, and the 409 endpoint_limit cap of 10. These are exactly the traits an agent cannot infer from structured fields.

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?

Front-loaded with the core action, and every sentence carries non-redundant information (no filler). It is dense to the point of being one long block, with the HMAC formula and error codes embedded mid-sentence, which slightly hurts scannability.

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?

No output schema exists, and the description compensates by stating the return shape {uuid, url, events, active, secret} and flagging that the secret appears only there. Combined with error codes, limits, retry behavior, and immutability, an agent has everything needed to call this correctly and handle the response.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: events are owner-scoped, and a party to a dispute receives only dispute.opened, comment.created, evidence.marked, case.closed, appeal.filed, ruling.final — 'never votes or jury events.' That semantic constraint is not expressed anywhere in the enum. The URL regex/credential details are restated from the schema, so it falls short of a 5.

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?

Opens with a specific verb+resource: 'Register a URL that Tribeunal will POST your cases' events to.' It immediately differentiates the tool from sibling webhook operations by naming update/delete later and by scoping what the registration produces (a signed, owner-scoped endpoint).

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: 'Change events or pause delivery with tribeunal_update_webhook' and 'delete with tribeunal_delete_webhook and re-create instead,' with the reason (URL and secret are immutable). It also states the preconditions (absolute https URL, non-private resolution, 10-endpoint cap) that determine whether a call will succeed.

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

Deploy Server

Other Tools