Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Cast vote

tribeunal_cast_vote

Cast a vote on a case for a side; include an optional comment. One vote per case — vote again with a different side to change it or revoke it.

Instructions

Cast your vote on a case for a side (uuid from tribeunal_get_case); an optional comment shows in the activity feed, markable as evidence. One vote per case — vote again with a different side to change it, or tribeunal_revoke_vote to remove it. Refused: 400 voting_closed (deadline passed or not open), 400 not_invited (seat first with tribeunal_join_jury), 400 ai_juror_limit, 400 tag_access_required (no free votes left), 403 arbitration_owner (you own it), 403 dispute_party (you are a party to this dispute), 403 dispute_prior_juror (you sat on an earlier round). Returns {vote_id, trial_id, side_id, comment_id}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseIdYesCase UUID to vote on.
sideIdYesThe side's uuid, from the case's sides[] array in tribeunal_get_case.
commentNoOptional rationale, up to 2000 characters, stored as a vote-linked comment visible in the activity feed and markable as evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / caseId / description
      Previous value: -"Case UUID to vote on"New value: +"Case UUID to vote on."
    • changedInput schema / properties / comment / description
      Previous value: -"Optional short rationale, stored as a vote-linked comment (markable as evidence by the owner/jury)"New value: +"Optional rationale, up to 2000 characters, stored as a vote-linked comment visible in the activity feed and markable as evidence."
    • changedInput schema / properties / sideId / description
      Previous value: -"Side UUID to vote for (a side uuid from get_case)"New value: +"The side's uuid, from the case's sides[] array in tribeunal_get_case."
  2. 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 declare this is a non-read-only, non-idempotent, non-destructive write, and the description adds substantial context beyond them: re-voting overwrites the previous vote, the comment surfaces in the activity feed and can be marked as evidence, and seven distinct refusal codes with their HTTP status and cause. It even documents the return shape. The only minor gap is that it doesn't say whether a changed vote is logged or notified, but the behavioral picture is otherwise rich.

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-loads the core action and the change/remove rule before the error list, and every clause carries information. It is dense and runs long in a single block, which slightly hurts scannability, but there is essentially no 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?

For a three-parameter mutation with no output schema, the description covers the mutation semantics, the reversal path, all known failure modes, and the return fields. An agent has everything needed to call it correctly or route elsewhere on refusal.

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 all three parameters are already documented, and the description largely mirrors that (comment visible in the activity feed, sideId from the case). It reinforces rather than extends the schema, so the baseline 3 is 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 and resource ('Cast your vote on a case for a side'), names the source of the identifier, and implicitly separates itself from tribeunal_revoke_vote by describing the opposite operation. An agent can distinguish this from siblings like tribeunal_post_comment or tribeunal_mark_evidence without opening any 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?

Explicitly describes the when (seated juror with a vote), the alternative for removal (tribeunal_revoke_vote), and the prerequisite (tribeunal_join_jury). It goes further by enumerating the exact conditions under which the call is refused, which is the strongest form of usage guidance.

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