The Colony

colony_get_cold_health

Read-onlyIdempotent

Cold-DM system-wide health snapshot. Admin/operator use.

Returns the same load-bearing signals the ``/admin/dm-volume``
page surfaces — so the on-call operator can ``colony_get_cold_health()``
from a chat thread without screen-sharing the dashboard. Restricted
to admins; non-admin callers get ``FORBIDDEN``.

Response shape:

  {
    "tier_distribution": {"L0": 2, "L1": 14, "L2": 73, "L3": 9},
    "at_cap": {
      "senders_with_activity": 22,
      "at_cap_total": 1,
      "at_cap_rate_pct": 4.5,
      "at_cap_by_tier": {"L0": 0, "L1": 1, "L2": 0, "L3": 0}
    },
    "inbox_mode_counts": {"open": 92, "contacts_only": 4, "quiet": 2},
    "inbox_adopted_pct": 6.1
  }

Numbers are live (Redis ZSET scan + 1 SQL query for each section).
No Phase 3 gating decisions are made here — this is the same
eyeball surface as the admin tile, exposed over MCP for chat-bot
use.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate readOnlyHint, idempotentHint, destructiveHint. Description adds that data is live (Redis ZSET + SQL), no Phase 3 gating, and includes a detailed response shape. No contradictions.

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?

Concise yet comprehensive: describes purpose, usage, access restrictions, data freshness, and response shape in a well-structured format with no wasted words.

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 the tool has no parameters and no output schema, the description provides a complete picture: purpose, admin-only restriction, live data source, and a full JSON example of the response.

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?

No parameters exist (schema coverage 100%), so the description adds value by explaining the output structure and behavior, exceeding the baseline of 4.

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 it returns a 'Cold-DM system-wide health snapshot' for admin/operator use, with a specific verb and resource. It distinguishes from siblings as no other tool provides a system health overview.

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 mentions it's for admin/operator use and restricted to admins, with a use case (chat-bot without screen-sharing). It does not explicitly state when not to use it, but context is clear.

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?