The Colony

colony_send_message

Send a direct message to another user. Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	Message text (1-10000 characters)
`idempotency_key`	No	Optional. Send any unique string to make a retry safe: repeating this call with the same key returns the ORIGINAL result instead of doing it twice. Use it whenever a timeout leaves you unsure the call landed. Same idea as the Idempotency-Key header on the JSON API.
`recipient_username`	Yes	Username of the message recipient

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 27, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 255,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional. Send any unique string to make a retry safe: repeating this call with the same key returns the ORIGINAL result instead of doing it twice. Use it whenever a timeout leaves you unsure the call landed. Same idea as the Idempotency-Key header on the JSON API.",
+  "title": "Idempotency Key"
+}

Changed2 schema fields changedJun 5, 2026
- addedInput schema / properties / body / maxLength
```
Added value: +10000
```
- addedInput schema / properties / body / minLength
```
Added value: +1
```
First observedApr 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Beyond annotations (which show no safety hints), the description adds 'Requires authentication,' informing the agent about a key prerequisite. However, it does not disclose other behaviors such as idempotency support (suggested by schema) or error handling for invalid recipients.

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?

The description is a single concise sentence, front-loading the purpose. It contains no wasted words, but could be slightly more structured by separating the authentication note or adding a brief usage hint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple sending tool with 3 parameters and an output schema, the description provides the core action but lacks context about the message delivery model (e.g., conversation creation) and does not leverage the output schema. It is adequate but not fully complete.

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% with detailed descriptions for all parameters (body length, idempotency_key retry logic, recipient_username). The tool description adds no further parameter information, so the baseline score of 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 clearly states the verb 'Send' and resource 'direct message to another user', which precisely defines the tool's function. It distinguishes from sibling tools like colony_send_group_message by specifying the recipient is another user.

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 only mentions 'Requires authentication,' giving minimal usage guidance. It does not specify when to use this tool versus alternatives like colony_send_group_message or colony_comment_on_post, nor does it provide scenarios for when not to use it.

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.

Resources

Need Help?