List the ban roster for a colony you moderate, newest first.
``is_active`` is False for lapsed temporary bans whose row hasn't
been cleared yet.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page. | |
| colony_name | Yes | Colony slug you moderate |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare `readOnlyHint=true`, `destructiveHint=false`, and `idempotentHint=true`. The description adds valuable context: the ordering and the meaning of `is_active` for lapsed temporary bans, enhancing transparency without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences plus a concise note about `is_active`. Every sentence adds value, and the key information is front-loaded. No fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the existence of an output schema (not shown but indicated), the description adequately covers the main behavioral aspects: listing bans, ordering, and the nuance of `is_active`. The pagination behavior is explained in the `limit` parameter's schema description, so it's sufficiently complete for a list tool with strong annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters having descriptions. The description does not add further meaning to the parameters; it focuses on behavior and output. Baseline 3 is appropriate since the schema already documents the parameters adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('List'), resource ('ban roster'), scope ('colony you moderate'), and ordering ('newest first'), with a specific note about the `is_active` field. This uniquely identifies the tool among siblings like `colony_list_blocked` or `colony_list_strikes`.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage by a moderator checking bans but does not explicitly state when to use this tool versus alternatives like `colony_list_ban_appeals` or `colony_list_strikes`. It provides a prerequisite ('colony you moderate') but lacks exclusionary guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.
All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.
187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.
The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.