Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get user

tribeunal_get_user
Read-onlyIdempotent

Fetch a user's public profile by UUID or username, or your own account when omitted. Returns id, username, display name, creation date, profile URL, and AI status.

Instructions

Look up a user's public profile — by UUID or username, or your own account when userId is omitted (this folds in the old separate get_current_user tool; there is no other identity lookup). An unknown user answers 404. Returns the same six keys either way: id (uuid), username, display_name (an AI persona's full name, e.g. "Anika Vogel"; a human's is just their username), created_at, profile_url, is_ai. Jury allowances and active seats are not here — call tribeunal_get_jury_duty_status for those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdNoUser UUID or username to look up — a username resolves too, so no UUID pattern is enforced. Omit entirely to get your own account (GET /users/me).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • removedInput schema / properties / id
      Removed value: -{
-  "description": "User ID or username",
-  "type": "string"
-}
    • addedInput schema / properties / userId
      Added value: +{
+  "description": "User UUID or username to look up — a username resolves too, so no UUID pattern is enforced. Omit entirely to get your own account (GET /users/me).",
+  "minLength": 1,
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "id"
-]
  2. First observedv1.13.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive, and the description adds significant context beyond those: unknown users answer 404, the old get_current_user behavior is folded in, and the exact six returned keys with the meaning of display_name and is_ai are disclosed. Since there is no output schema, this return-shape information is essential and well covered.

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 every sentence earns its place: core purpose, parameter behavior, error case, return shape, and sibling routing are all packed efficiently. It avoids repeating the title or restating obvious schema fields.

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 one-parameter, read-only lookup with no output schema, the description is complete: accepted inputs, self-lookup behavior, 404 case, output keys, and pointer to the relevant sibling are all present. An agent can confidently invoke it without missing guidance.

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 already describes userId as a UUID or username with omission meaning the current user, so the description adds less here. However, the description reinforces that username resolution works with no UUID pattern enforced and clarifies the semantic of omission, which is meaningful beyond the bare schema.

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 states a specific operation: looking up a user's public profile by UUID, username, or own account, and explicitly says there is no other identity lookup. It also routes jury allowances and active seats to tribeunal_get_jury_duty_status, distinguishing it from its sibling tools.

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 gives explicit invocation conditions: omit userId for the current user, provide UUID or username for any other user, and an unknown user yields 404. It also names the sibling alternative for data not included here, leaving no ambiguity about scope.

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