Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Unmark evidence

tribeunal_unmark_evidence
Idempotent

Unmark evidence on a comment or case file to reverse a previous marking, enabling comment deletion or restoring the item's original state.

Instructions

Remove an evidence mark from a comment or case file, reversing tribeunal_mark_evidence (case owner or jury only — no self-comment restriction here). Already-unmarked 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. Unmarking a comment is required before tribeunal_delete_comment can remove it. Returns the item with isEvidence false, markedBy null: 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 unmark, matching kind — the same uuid tribeunal_list_evidence returns for that item.
kindYes'comment' for a posted comment (ids from tribeunal_list_comments) or 'file' for a case file (ids from tribeunal_list_evidence, kind: file).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 unmark, matching kind — the same uuid tribeunal_list_evidence returns for that item."
    • 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 unmark: 'comment' or 'file' (case file)"New value: +"'comment' for a posted comment (ids from tribeunal_list_comments) or 'file' for a case file (ids from tribeunal_list_evidence, kind: file)."
  2. First observedv1.13.0

TDQS

A5/5.0
Behavior5/5

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

The description adds behavioral context beyond annotations: idempotency (already-unmarked is a no-op), the case-freeze error condition with instruction not to retry, and the exact return shape for both comment and file. This complements the annotations (idempotentHint=true, readOnlyHint=false) without contradiction.

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 but each sentence earns its place: purpose, permissions, idempotency, freeze behavior, dependency, and return formats. It is logically ordered with key information front-loaded, and while long, it avoids redundancy and remains scannable.

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 mutation tool with no output schema, this description covers everything an agent needs: what it does, permissions, idempotency, error handling, prerequisite usage, and return shapes for both item types. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters have full schema coverage (100%) with detailed descriptions. The description adds sourcing guidance: id should match tribeunal_list_evidence UUIDs, and kind references tribeunal_list_comments vs tribeunal_list_evidence. This provides cross-tool context that the schema alone lacks.

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 explicitly states the verb 'remove', the resource 'an evidence mark from a comment or case file', and names the sibling it reverses (tribeunal_mark_evidence). This is highly specific and distinguishes it from related tools like tribeunal_delete_comment or tribeunal_list_evidence.

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?

Provides explicit when-to-use conditions: case owner or jury only, no self-comment restriction, required before deleting a comment, and clearly explains the freeze scenario (403 evidence_frozen) telling the agent not to retry. It also names the reverse operation (tribeunal_mark_evidence) as an alternative.

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