Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Await case activity

tribeunal_await_case_activity
Read-only

Block until a new event appears on a case; returns event data and a cursor to re-arm on timeout for continuous monitoring.

Instructions

Block until a NEW event appears on a case (long-poll, up to timeoutS seconds) — for a one-shot read use tribeunal_get_case_activity; for the final decision use tribeunal_await_verdict. Omit after to watch from now; on re-arm pass the previous latestCursor so nothing is missed. Returns {events, latestCursor, hasMore, caseUuid, caseState, caseEndsAt, verdict, timedOut, waitedS}. PROTOCOL: if timedOut is true, no event arrived yet — re-arm by calling again with after=latestCursor. Check caseEndsAt and STOP re-arming well past it (tell the human instead of looping forever).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoCursor to watch from (a previous latestCursor); omit to anchor at the current tail ("watch from now").
typesNoOnly wake for these event types — same enum as tribeunal_get_case_activity.
caseIdYesCase UUID to watch.
timeoutSNoSeconds to block, 5-170; defaults to 120. On timeout, re-arm with the returned latestCursor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / after / description
      Previous value: -"Cursor to watch from; omit to anchor at the current tail (\"watch from now\")"New value: +"Cursor to watch from (a previous latestCursor); omit to anchor at the current tail (\"watch from now\")."
    • changedInput schema / properties / caseId / description
      Previous value: -"Case UUID to watch"New value: +"Case UUID to watch."
    • changedInput schema / properties / timeoutS / description
      Previous value: -"Seconds to block (5-170). On timeout, re-arm with the returned latestCursor."New value: +"Seconds to block, 5-170; defaults to 120. On timeout, re-arm with the returned latestCursor."
    • changedInput schema / properties / types / description
      Previous value: -"Only wake for these event types"New value: +"Only wake for these event types — same enum as tribeunal_get_case_activity."
    • changedInput schema / properties / types / items / enum
      Previous value: -[
-  "vote",
-  "vote_revoked",
-  "comment",
-  "evidence_marked",
-  "evidence_unmarked",
-  "jury_joined",
-  "trial_closed",
-  "trial_reopened"
-]New value: +[
+  "vote",
+  "vote_revoked",
+  "comment",
+  "evidence_marked",
+  "evidence_unmarked",
+  "jury_joined",
+  "jury_left",
+  "trial_closed",
+  "trial_reopened",
+  "trial_updated"
+]
  2. First observedv1.13.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide readOnlyHint=true and destructiveHint=false, but the description adds critical behavioral context beyond that: the long-poll blocking mechanism, timeout handling, re-arm protocol, and the instruction to stop looping past caseEndsAt. It also explains the timedOut flag and return structure. This fully discloses the tool's runtime behavior.

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 well-structured: the first sentence states purpose and alternatives, the second gives re-arm guidance, the third lists return fields, and the fourth is a PROTOCOL block. Every sentence provides essential information; no fluff. It is front-loaded with the core purpose and alternatives.

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?

Given the tool's complexity (blocking, timeout, re-arm, return fields) and the absence of an output schema, the description fully covers all necessary information: what it returns, when to re-arm, how to stop, and how it relates to siblings. No missing detail prevents correct usage.

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% with descriptive parameter text, so baseline is 3. The description adds value by explaining the 'after' cursor semantics ('omit to watch from now; on re-arm pass the previous latestCursor') and the timeout default/range, and ties them to the re-arm protocol. It does not repeat schema definitions but clarifies usage patterns.

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 ('Block until'), resource ('a NEW event appears on a case'), and the blocking behavior with timeout. It explicitly distinguishes from siblings by naming tribeunal_get_case_activity (one-shot read) and tribeunal_await_verdict (final decision). This leaves no ambiguity about what the tool does.

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 provides when to use vs alternatives ('for a one-shot read use tribeunal_get_case_activity; for the final decision use tribeunal_await_verdict'). It also gives operational guidance for re-arming with after=latestCursor and the stopping rule based on caseEndsAt, making usage conditions clear.

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