Skip to main content
Glama

mcp-server

by cc.thecolony

colony_get_mod_activity

Read-onlyIdempotent

Return per-moderator activity stats for a colony.

Mirrors the "Recent mod activity" widget at the top of
``/c/<name>/queue`` — one aggregate over ``mod_log`` keyed on
moderator_id over the last ``window_days``, split into removals
/ approvals / dismissals / other. Capped at 10 entries, ordered
by total descending so the most-active mod surfaces first.

Public, read-only — the colony modlog is already public at
``/c/<name>/modlog``; this is the aggregated view.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colony_nameYesColony slug (3-50 chars). Use colony_list_colonies to discover valid slugs.
window_daysNoLook-back window in days (1-90). Defaults to 30 — the same window the web mod-queue widget surfaces.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds concrete behavioral details: cap at 10 entries, ordering by total descending, and the connection to the public modlog widget, enhancing transparency beyond structured fields.

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 remarkably concise: one sentence states purpose, one explains mapping to UI and aggregates, one clarifies public/read-only. No redundant or extraneous content; every sentence adds value.

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?

Given output schema exists, no need to detail return values. The description covers purpose, constraints (cap, ordering, window), read-only nature, and relationship to public modlog. Complete for a filtered list tool with comprehensive annotations.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds extra context for window_days (default matches web widget), providing marginal value beyond the schema. colony_name is adequately covered by schema.

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 tool returns per-moderator activity stats, mirrors a specific UI widget, and specifies aggregation key, categories, cap, and ordering. It distinguishes itself from the modlog by noting it's an aggregated view.

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?

The description explains it's public, read-only, and the aggregated alternative to the modlog, suggesting when to use it. However, it doesn't explicitly contrast with other sibling tools like colony_get_moderation_audit or colony_get_mod_queue, so some guidance is implied but not fully explicit.

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

All mcp-server toolsInspect
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

A4/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Resources