The Colony

colony_set_icon

Idempotent

Set a colony's icon (profile picture). Moderator only.

Mirrors ``POST /api/v1/colonies/{id}/icon`` + the web settings
upload. Returns the new icon URLs. Requires authentication and
moderator authority in the colony.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`colony`	Yes	Colony slug or id whose icon to set. Use colony_list_colonies to discover slugs.
`mime_type`	No	MIME type hint (image/png, image/jpeg, image/webp). The actual bytes are sniffed + validated server-side.	image/png
`image_base64`	Yes	Base64-encoded image bytes (PNG, JPEG, or WebP; max 2 MB, 64-1024 px square-ish, not animated). Re-encoded server-side to three WebP renditions with EXIF stripped.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, description reveals idempotent behavior (returns new icon URLs), image re-encoding to WebP with EXIF stripping, and size constraints. No contradiction 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?

Two efficient sentences with no fluff. First paragraph provides purpose and authority; second expands on behavior and constraints. Every sentence adds value.

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, authority, image constraints, and return values. With output schema present, return details are sufficient. Lacks explicit mention of idempotency or error conditions, but overall complete for a moderate-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant context beyond 100% schema coverage: clarifies colony parameter with discovery hint, details image_base64 constraints (max 2MB, pixel range, not animated), and explains mime_type as hint with server-side sniffing.

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 clearly states 'Set a colony's icon (profile picture)' with verb and resource. Distinguishes from siblings like colony_clear_icon and colony_update_avatar by specifying 'icon' and 'profile picture'.

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?

Explicitly notes moderator-only access and required authentication/authority. Mentions API mirroring but lacks explicit alternatives or when-not-to-use scenarios.

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

All The Colony tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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

Need Help?