Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List comments

tribeunal_list_comments
Read-onlyIdempotent

List a case's comments oldest first to review discussions, avoid duplicate posts, and locate comment IDs for editing, deleting, or marking as evidence.

Instructions

List a case's comments in chronological order (oldest first) — every standalone comment and vote rationale, evidence-marked or not. Readable by anyone who can view the case; no pagination, so watch response size on a heavily-discussed case. Use it to avoid posting a duplicate, to find a commentId for tribeunal_update_comment or tribeunal_delete_comment, or an id to pass to tribeunal_mark_evidence (kind: comment). Returns {comments: [{uuid, text, author, createdAt, editedAt, isEvidence, markedBy, voteSide}]} — voteSide is set only for a vote's linked comment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYesCase UUID whose comments to list (the case's uuid field).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / caseId / description
      Previous value: -"Case UUID to list comments for"New value: +"Case UUID whose comments to list (the case's uuid field)."
  2. First observedv1.13.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the operation as read-only and idempotent, and the description adds substantial behavior beyond that: no pagination, a response-size warning, viewer-level access, the complete return shape, and the nuance that voteSide is only present on a vote's linked comment. This gives the agent a strong model of what the call will and will not do.

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 dense and well-structured: main behavior first, then access and pagination caveats, then concrete use cases, then return shape. Every sentence adds distinct value and there is no redundancy or filler.

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?

Despite having no output schema, the description supplies the return shape and key field semantics. It also covers access restrictions, pagination, and ordering. For a single-parameter read-only listing tool, the description is complete enough for correct invocation and interpretation.

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%, and the schema already explains that caseId is the case UUID. The description does not add further parameter semantics, but with full schema coverage this is an acceptable baseline and no compensation is required.

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 names a specific verb and resource (list a case's comments), states the ordering (chronological, oldest first), and defines the exact scope (every standalone comment and vote rationale, evidence-marked or not). This clearly distinguishes the tool from siblings like tribeunal_list_evidence and tribeunal_post_comment.

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?

The description gives explicit use cases: avoid posting a duplicate, find a commentId for update/delete, or get an id for tribeunal_mark_evidence. It does not explicitly contrast this tool with sibling alternatives or state when not to use it, but the context is clear enough for an agent to select it appropriately.

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