Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mark evidence

tribeunal_mark_evidence
Idempotent

Marks another user's comment or a case file as arbitration evidence; case owner or jury only, never your own comment; returns the updated evidence record.

Instructions

Mark another user's comment or a case file as evidence — case owner or jury only, never your own comment; already-marked is a no-op. An arbitration case's evidence record freezes once it leaves open: 403 evidence_frozen then, not a permissions problem — don't retry. id is the comment or file uuid. Listed via tribeunal_list_evidence; reversed by tribeunal_unmark_evidence. Returns the item with isEvidence true and markedBy set: a comment as {uuid, text, author, createdAt, editedAt, voteSide}, a file as {uuid, title, originalName, mimeType, size, url, thumbnailUrl, sortOrder, createdAt}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID of the comment or case file to mark, matching kind.
kindYes'comment' to mark a posted comment (ids from tribeunal_list_comments), or 'file' to mark an uploaded case file (case files are attached when a case is created on the website; no tool uploads one).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • changedInput schema / properties / kind / description
      Previous value: -"'comment' to mark a posted comment (ids from tribeunal_list_comments), or 'file' to mark an uploaded case file (case files are uploaded from the case web page — there is no MCP upload tool)."New value: +"'comment' to mark a posted comment (ids from tribeunal_list_comments), or 'file' to mark an uploaded case file (case files are attached when a case is created on the website; no tool uploads one)."
  2. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"UUID of the comment or case file"New value: +"UUID of the comment or case file to mark, matching kind."
    • addedInput schema / properties / id / pattern
      Added value: +"^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
    • changedInput schema / properties / kind / description
      Previous value: -"What to mark: 'comment' or 'file' (case file)"New value: +"'comment' to mark a posted comment (ids from tribeunal_list_comments), or 'file' to mark an uploaded case file (case files are uploaded from the case web page — there is no MCP upload tool)."
  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 only give the generic safety profile (idempotent, non-destructive), while the description adds the non-obvious failure mode: a frozen evidence record returns 403 evidence_frozen and must not be retried, and that this is not a permissions error. That distinction is exactly the context an agent needs to avoid pointless retry loops.

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?

Dense but front-loaded: the action, the authorization rule, and the failure mode all appear before the return-value detail. It is a single unstructured block rather than segmented prose, which slightly hurts scanability, but every clause carries information.

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 compensates by spelling out the return payload for both item types (comment vs file field lists). Combined with authorization rules and the frozen-case error, an agent has everything needed to call and interpret the result.

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% and the enum already documents kind, so the schema carries most of the load. The description still adds meaning by tying id to the specific id source per kind and by enumerating the returned shape for a comment versus a file, which clarifies what kind actually selects.

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 (mark) and resource (evidence), scoped precisely to another user's comment or a case file. It clearly separates this from submit_evidence (uploading) and list_evidence (enumeration), so an agent can route correctly without opening schemas.

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 states when it applies (case owner or jury only), a hard exclusion (never your own comment), and a degenerate case (already-marked is a no-op). It also names tribeunal_list_evidence as the discovery path and tribeunal_unmark_evidence as the reversal, covering the full lifecycle.

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