Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get case activity

tribeunal_get_case_activity
Read-onlyIdempotent

Read a page of a case's activity feed as a cursorable event stream to track votes, comments, evidence, jury changes, and verdicts.

Instructions

Read a page of a case's activity feed (votes, comments, evidence marks, jury joins, case edits, jury departures, closure) as a cursorable event stream. Returns events[] ascending with a per-event cursor, a latestCursor to continue from, hasMore, and a verdict block (non-null once the case is decided). Use this for a one-shot read; to BLOCK until something happens, use tribeunal_await_case_activity or tribeunal_await_verdict instead. To read the content itself, use tribeunal_list_comments or tribeunal_list_evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOpaque cursor from a previous response's latestCursor; omit to read the tail (latest events).
limitNoMax events per page, 1-100; defaults to 50.
typesNoRestrict to these event types (vote, vote_revoked, comment, evidence_marked, evidence_unmarked, jury_joined, jury_left, trial_closed, trial_reopened, trial_updated, dispute_opened, appeal_filed, ruling_final); omit for all types.
caseIdYesCase UUID whose activity to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.0
    • changedInput schema / properties / types / description
      Previous value: -"Restrict to these event types (vote, vote_revoked, comment, evidence_marked, evidence_unmarked, jury_joined, jury_left, trial_closed, trial_reopened, trial_updated); omit for all types."New value: +"Restrict to these event types (vote, vote_revoked, comment, evidence_marked, evidence_unmarked, jury_joined, jury_left, trial_closed, trial_reopened, trial_updated, dispute_opened, appeal_filed, ruling_final); omit for all types."
    • changedInput schema / properties / types / items / enum
      Previous value: -[
-  "vote",
-  "vote_revoked",
-  "comment",
-  "evidence_marked",
-  "evidence_unmarked",
-  "jury_joined",
-  "jury_left",
-  "trial_closed",
-  "trial_reopened",
-  "trial_updated"
-]New value: +[
+  "vote",
+  "vote_revoked",
+  "comment",
+  "evidence_marked",
+  "evidence_unmarked",
+  "jury_joined",
+  "jury_left",
+  "trial_closed",
+  "trial_reopened",
+  "trial_updated",
+  "dispute_opened",
+  "appeal_filed",
+  "ruling_final"
+]
  2. Changed6 schema fields changedv2.0.0
    • changedInput schema / properties / after / description
      Previous value: -"Opaque cursor from a previous response; omit for the tail (latest events)"New value: +"Opaque cursor from a previous response's latestCursor; omit to read the tail (latest events)."
    • changedInput schema / properties / caseId / description
      Previous value: -"Case UUID whose activity to read"New value: +"Case UUID whose activity to read."
    • changedInput schema / properties / limit / description
      Previous value: -"Max events (1-100, default 50)"New value: +"Max events per page, 1-100; defaults to 50."
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / types / description
      Previous value: -"Restrict to these event types"New value: +"Restrict to these event types (vote, vote_revoked, comment, evidence_marked, evidence_unmarked, jury_joined, jury_left, trial_closed, trial_reopened, trial_updated); omit for all types."
    • 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"
+]
  3. First observedv1.13.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real behavioral context: ascending event ordering, cursor semantics, hasMore pagination, and a verdict block that is non-null only once decided. It does not mention auth/permission requirements, so it falls short of the top score.

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, then return shape, then routing to alternatives — three dense sentences with little waste. The parenthetical event-type enumeration slightly overlaps the schema's types enum, a minor redundancy.

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?

With no output schema, the description carries the return-value burden and does so completely (events[], per-event cursor, latestCursor, hasMore, verdict block). Combined with the alternative-routing guidance, an agent has everything needed to call and interpret this correctly.

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 the schema already documents after/limit/types/caseId fully. The description's 'cursorable event stream' lightly reinforces the 'after' cursor concept but adds no syntax or format detail beyond the schema, making baseline 3 appropriate.

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?

States a specific verb+resource (read a case's activity feed) and enumerates the scope it covers (votes, comments, evidence marks, jury joins/leaves, edits, closure). It explicitly differentiates from siblings by naming the await variants and content-listing tools, so an agent can select it without opening a schema.

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?

Gives explicit when-to-use ('one-shot read') and when-not-to-use with named alternatives: block instead with tribeunal_await_case_activity / tribeunal_await_verdict, and fetch content with tribeunal_list_comments / tribeunal_list_evidence. Nothing is left to inference.

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