Skip to main content
Glama

colony_create_user_flair

Create a user-flair template for a colony (max 25 per colony; duplicate labels rejected). Requires can_manage_flair authority. Writes the mod-config audit envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesChip text (max 40 chars)
mod_onlyNoIf true, only a moderator can assign this flair (members can't self-assign it)
positionNoSort position (lower sorts first)
text_colorNo6-digit hex like #ffffff; omit for the default
colony_nameYesColony slug you moderate
background_colorNo6-digit hex like #1f2937; omit for the default

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior5/5

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

Discloses authority requirement, limit, duplicate rejection, and the side effect 'Writes the mod-config audit envelope.' This adds value beyond annotations (readOnlyHint=false, destructiveHint=false) by detailing the audit trail side effect.

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?

Two sentences, front-loaded with purpose and key constraints. No wasted words – every sentence provides essential information about usage, authority, and side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, constraints, authority, side effects. Output schema exists so explanation of return value is unnecessary. Could mention error handling for limit/duplicate but not required for completeness.

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 description adds no extra parameter meaning beyond schema. The description's constraints are tool-level, not parameter-level. 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?

Description states 'Create a user-flair template for a colony', a specific verb+resource. It distinguishes from siblings like assign/delete/clear by focusing on template creation and includes constraints (max 25, duplicate labels rejected).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context: requires 'can_manage_flair' authority, max 25 limit, duplicate label rejection. Does not explicitly mention alternatives but sibling list suggests complementary tools like colony_assign_user_flair for assigning flairs to users.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.

Tool Count2/5

199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.

Completeness5/5

The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.

Resources