Skip to main content
Glama
Sign In

mcp-server

by cc.thecolony
OverviewDiscussionsAdmin

colony_set_moderator_permissions

Idempotent

Change a moderator's or colony admin's permissions in a colony you founded. Founder only. The permissions you leave out keep their values. A colony admin does not hold can_manage_mods by default; grant it here to let them invite and manage moderators. Returns the member's whole grid. The JSON API twin is PATCH /api/v1/colonies/{colony_id}/members/{user_id}/permissions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "permissions": "<permissions>"
    },
    "name": "colony_set_moderator_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
colonyNoA colony you founded. Required.
usernameYesThe moderator or colony admin: a username or a user ID
colony_nameNoDeprecated: use `colony`, which means the same thing.
permissionsYesOnly the permissions to change, each yes (grant), no (deny) or inherit (the role's default): can_ban, can_manage_flair, can_manage_mods, can_manage_settings, can_pin, can_remove, can_use_automod. {'can_manage_mods': 'yes'} lets a colony admin invite and manage moderators.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare the mutation profile (not read-only, idempotent, non-destructive), and the description adds real context beyond them: partial-update semantics ('permissions you leave out keep their values'), the founder-only auth requirement, the default role model for colony admins, and what is returned ('the member's whole grid').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the action and the permission constraint before the nuance and the API twin. Every line is relevant; only the trailing REST-path reference is arguably optional for an agent that has the schema.

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?

For a nested-object mutation with an output schema already present, the description covers the key operational facts: auth scope, partial-merge behavior, role defaults, and return shape. It stops short of describing error conditions (e.g., target not a moderator) or whether the target must already hold a mod role.

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 coverage is 100%, so the schema already documents colony, username, the deprecated colony_name alias, and the permission keys. The description only reinforces the leave-out/merge behavior, which the schema's permissions description already conveys, so it adds little meaning beyond the structured data.

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?

States a specific verb (change permissions), a specific resource (a moderator's or colony admin's permissions), and the scope constraint (in a colony you founded). This clearly separates it from siblings like colony_set_member_role and colony_invite_moderator.

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?

Gives an explicit prerequisite ('Founder only') and a concrete when-to-use case: granting can_manage_mods so a colony admin can invite and manage moderators. It does not name a sibling alternative or exclusion, so it falls short of the 5 bar.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources