Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get tribe

tribeunal_get_tribe
Read-onlyIdempotent

Fetch a tribe's core details (name, description, intro, visibility, owner, tags, timestamps) by UUID. For private tribes you own, also get a shareable URL for view-only access.

Instructions

Read one tribe's details — name, description, intro, visibility, owner, tags and timestamps — not its member roster; read that with tribeunal_list_tribe_members (member/owner/admin only). A private tribe is readable only by its owner, members and pending invitees; to everyone else it 404s, identical to an unknown tribe. For a private tribe you own, the response also carries a shareUrl: a view-only link (joining still needs an invite) — rotate it from the tribe's web page. Change these fields with tribeunal_update_tribe; remove the tribe with tribeunal_delete_tribe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTribe UUID — the tribe's uuid field, not its slug or numeric id. Get one from tribeunal_list_tribes or a tribeunal_create_tribe response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Tribe UUID (the tribe's uuid field, not its slug or numeric id)"New value: +"Tribe UUID — the tribe's uuid field, not its slug or numeric id. Get one from tribeunal_list_tribes or a tribeunal_create_tribe response."
  2. First observedv1.13.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only and idempotent, and the description adds substantial behavioral context beyond that: private-tribe visibility rules, the deliberate 404 for unauthorized views, the owner-only shareUrl field, the view-only nature of the link, and rotation via the web page. No contradictions with annotations.

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, access-control edge cases, shareUrl behavior, and sibling routing. Key information is front-loaded before secondary details, with no repeated schema content 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?

For a single-parameter read tool with strong annotations, the description covers everything an agent needs: what is returned, what is not, access restrictions, 404 semantics, the shareUrl special case, and related mutation tools. No missing context would cause an incorrect call.

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 id is a tribe UUID, not a slug or numeric id, and where to obtain it. The main description adds no additional parameter meaning, so the baseline of 3 applies correctly.

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 uses a specific verb ('Read') and resource ('one tribe's details'), then enumerates the exact fields returned: name, description, intro, visibility, owner, tags and timestamps. It explicitly distinguishes itself from tribeunal_list_tribe_members, so an agent can select it 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?

It states when to use this tool (read tribe details) and when not to (read member roster), naming the exact sibling tribeunal_list_tribe_members and its access restriction. It also points to tribeunal_update_tribe and tribeunal_delete_tribe for mutation, giving clear routing among alternatives.

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