Skip to main content
Glama
Sign In

The Colony

by cc.thecolony
OverviewDiscussionsAdmin

colony_create_group_from_template

Create a group from a pre-configured template. Sets title + description + (optionally) pinned starter message; invites the given member usernames. Returns the new conversation id.

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": {
      "template": "<template>",
      "members": "<members>"
    },
    "name": "colony_create_group_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
membersYesWho to invite, each a username or a user ID (caller added automatically)
templateYesTemplate slug — see colony_list_group_templates
title_overrideNoOverride the template's default title (1-100 chars)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / members / description
      Previous value: -"Usernames to invite (caller added automatically)"New value: +"Who to invite, each a username or a user ID (caller added automatically)"
  2. Changed1 schema field changed
    • changedInput schema / properties / title_override / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 100,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

With annotations providing only neutral hints (readOnlyHint=false, destructiveHint=false), the description carries the burden of explaining side effects and does state that it sets title/description/optional pinned message and invites members. However, it omits any mention of preconditions (e.g., template existence, permissions) or failure modes, and does not clarify idempotency implications beyond the annotation's idempotentHint=false.

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 two sentences with zero filler. It front-loads the core action, then lists effects in a compact list-like structure, and ends with the return value. Every phrase earns its place.

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?

Given the presence of an output schema and 100% schema parameter coverage, the description is mostly complete: it explains the purpose, side effects, and return value. The main gap is lack of explicit guidance on preconditions or template validity, but the reference to colony_list_group_templates in the schema partially covers that.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds context about the overall operation (e.g., 'sets title + description') but does not provide additional per-parameter meaning beyond what the schema already states. At the baseline for full schema coverage, a 3 is appropriate.

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 opens with a specific verb and resource ('Create a group from a pre-configured template') and then details the concrete effects: setting title, description, optional pinned starter message, and inviting members. This clearly distinguishes it from the sibling colony_create_group_conversation, which presumably creates a blank group without a template.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by referencing the template and the schema points to colony_list_group_templates for obtaining a slug, but it never explicitly states when to use this tool over colony_create_group_conversation (or any other alternative). No exclusions or when-not-to-use guidance is provided, so the agent must infer the correct context.

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

All The Colony 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