Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Invite tribe members

tribeunal_invite_tribe_members

Invite members to a private tribe via usernames or emails, with independent per-invite resolution to avoid batch failures.

Instructions

Invite people into a private tribe you own (or any, as admin) by username or email — recruitment, not membership: an invitee joins just by opening the tribe page while logged in (API callers can also POST join explicitly). Each of up to 50 invitees resolves independently, so one bad name never fails the batch. Public tribes are already open to everyone; inviting into one returns 400. See tribeunal_list_tribe_members for the roster, tribeunal_remove_tribe_member to undo it. To put people on one case's jury instead of into the tribe, use tribeunal_invite_jurors (its tribeId recruits this whole tribe at once). Returns {status, tribe, results[], summary} — summary counts invited, already_invited, already_member, not_found and self.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tribeIdYesUUID of the private tribe to invite into — from tribeunal_list_tribes. You must own it or be an admin.
inviteesYes1–50 usernames or email addresses. Each is resolved and reported independently, so one bad entry never fails the rest of the batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / invitees / description
      Previous value: -"Usernames or email addresses to invite (maximum 50 per call)"New value: +"1–50 usernames or email addresses. Each is resolved and reported independently, so one bad entry never fails the rest of the batch."
    • addedInput schema / properties / invitees / items / minLength
      Added value: +1
    • changedInput schema / properties / tribeId / description
      Previous value: -"Tribe UUID to invite people into (the tribe's uuid field, not its slug or numeric id) — private tribes only"New value: +"UUID of the private tribe to invite into — from tribeunal_list_tribes. You must own it or be an admin."
  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 indicate readOnlyHint=false, idempotentHint=false, etc., but the description adds critical behavioral details: the batch independence ('each invitee resolves independently'), the recruitment model ('an invitee joins just by opening the tribe page'), and the error condition for public tribes. It also describes the return structure and summary counts, which are not in 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 ~100 words but every sentence earns its place: purpose, nuance, batch behavior, public-tribe restriction, alternatives, and return format. It is front-loaded with the main action and structured logically. No filler or redundancy.

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 two-parameter tool with no output schema, the description covers all necessary context: how to invite, constraints (private only, admin requirement), what happens with invalid entries, what to expect in the response, and how it differs from sibling tools. An agent has everything it needs to call this correctly.

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 coverage is 100% (both parameters have detailed descriptions), so baseline is 3. The description does not add significant new meaning beyond the schema: it repeats the '1–50 usernames or email addresses' and the independent resolution, both already in the schema. The only slight addition is the 'from tribeunal_list_tribes' hint for tribeId, which is also in the schema. Thus it adds little beyond what the schema already conveys.

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 clearly states the action (invite), the target (private tribe members), and the method (by username or email). It explicitly distinguishes itself from related tools like tribeunal_list_tribe_members, tribeunal_remove_tribe_member, and tribeunal_invite_jurors, and even clarifies the recruitment-vs-membership nuance. This leaves no ambiguity about what the tool does.

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 explicitly states when to use it ('private tribe you own or any as admin'), when not to ('Public tribes are already open to everyone; inviting into one returns 400'), and provides alternatives for related actions ('See tribeunal_list_tribe_members for the roster... To put people on one case's jury... use tribeunal_invite_jurors'). This is textbook 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