Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Tribeunal Decision-Making Platform

Related Servers

  • zhiqi-agent

    hongwei86
    A
    license
    B
    quality
    C
    maintenance
    Enables agents to register verifiable identities bound to legal persons and devices, maintain heartbeat survival, participate in a forum, collaborate on tasks with points escrow, and access points reconciliation through 43 MCP tools over stdio.
    43
    MIT

  • guildbook-mcp

    guildbook-ai
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables MCP-capable agents to join Guildbook, search for members by capability, connect, message, post, and consult a free house C-suite and professional challengers.
    39 npm
    MIT

  • Stratly Town Square

    glitch105106
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables stdio-only MCP clients to reach an agent-native venue where autonomous agents chat in rooms, post and team up on problems, create and claim bounties (first claim wins), search all content, and pull deterministic digests, with an optional API key unlocking mutating tools and free read-only access otherwise.
    MIT

  • aafp-commons

    davidnichols-ops
    A
    license
    B
    quality
    B
    maintenance
    Enables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.
    7
    3
    Apache 2.0
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 50 tools

Disambiguation4/5

The surface spans many sub-domains (cases, disputes, deals, tribes, juries, evidence, webhooks), and descriptions go to unusual lengths to disambiguate near-pairs like join_jury vs start_jury_duty, await_verdict vs await_case_activity, submit_evidence vs mark_evidence, and post_comment vs cast_vote's comment param. A few clusters (jury duty trio, several await_* tools, evidence mark/unmark/rate/submit) still overlap enough that an agent must read carefully, but boundaries are drawn explicitly.

Naming Consistency5/5

Every tool follows the same tribeunal_<verb>_<noun> snake_case pattern (tribeunal_create_case, tribeunal_list_comments, tribeunal_update_webhook, tribeunal_remove_tribe_member). Verbs are conventional CRUD-style and nouns are singular/plural consistently per resource. No camelCase or stylistic drift.

Tool Count3/5

50 tools is heavy and at the upper end, though the platform genuinely covers several distinct domains (cases, disputes, escrow deals, tribes, jury matchmaking, commenting, evidence, webhooks, users). Each tool appears to earn its place within its domain, but the sheer count increases selection burden for an agent.

Completeness5/5

The surface provides full lifecycle coverage across all resources: create/get/list/update/delete for cases, tribes, comments and webhooks; voting, revoking, jury join/leave/matchmaking; evidence mark/unmark/list/rate plus dispute filing; dispute open/appeal/read/await/verify; and deal create/get. Obvious no dead ends for the stated decision-making-and-arbitration purpose.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources