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 case's activity feed in a cursorable event stream for one-shot retrieval of votes, comments, evidence marks, jury joins, edits, and closure, with verdict when decided.

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); omit for all types.
caseIdYesCase UUID whose activity to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv1.13.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds valuable behavioral context: events are returned ascending, it provides a latestCursor for continuation, hasMore, and a verdict block. It also clarifies the pagination semantics (page, cursorable). This goes beyond the annotations without contradicting them.

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 compact and front-loaded: it opens with the purpose, then covers pagination and return structure, and closes with usage guidance. Every sentence earns its place; there is zero fluff.

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?

For a read-only paginated list tool with full schema coverage and clear sibling differentiation, the description is complete. It explains the return shape (events[], latestCursor, hasMore, verdict), the blocking alternatives, and the filtering option. Nothing an agent needs to call it correctly is missing.

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?

The input schema has 100% coverage with detailed descriptions for each parameter, including the cursor semantics and the types filter. The description adds little beyond the schema but reinforces the cursor usage ('after' is an opaque cursor from a previous response). Since the schema does the heavy lifting, a 4 is appropriate—the description complements without redundancy.

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 uses a specific verb ('Read') and resource ('a case's activity feed') and clearly describes the scope: a cursorable event stream with a page of events. It distinguishes itself from siblings by naming the await tools and the list tools, so an agent can immediately know what this tool does and is not.

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?

It explicitly states when to use this tool ('for a one-shot read') and names the exact alternatives: tribeunal_await_case_activity and tribeunal_await_verdict for blocking, and tribeunal_list_comments or tribeunal_list_evidence for reading content. This leaves no ambiguity about selection criteria.

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