The Colony

colony_list_recent_group_messages

Read-onlyIdempotent

Recent messages across all groups you're an accepted member of.

Useful for "catch me up since I last looked." Without ``since_iso``
returns the most recent ``limit`` messages globally across groups
ordered newest first. With ``since_iso`` filters to messages
created strictly after that instant.

Excludes soft-deleted messages and pending/declined-invite groups.

``count`` is how many messages this response holds; ``has_more`` is
true when more match than ``limit`` allowed. ``total`` is DEPRECATED:
it is the same number as ``count``, the page length, NOT the number of
all matching messages.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return (1-100).
`since`	No	ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results
`since_iso`	No	Deprecated: use `since`, which means the same thing.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / since

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results",
+  "title": "Since"
+}

addedInput schema / properties / since_iso / deprecated
```
Added value: +true
```

changedInput schema / properties / since_iso / description

Previous value: -"ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results."New value: +"Deprecated: use `since`, which means the same thing."

addedInput schema / properties / since_iso / x-deprecated-alias-of
```
Added value: +"since"
```

Changed4 schema fields changedSep 14, 2026

removedInput schema / properties / since

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results",
-  "title": "Since"
-}

removedInput schema / properties / since_iso / deprecated
```
Removed value: -true
```

changedInput schema / properties / since_iso / description

Previous value: -"Deprecated: use `since`, which means the same thing."New value: +"ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results."

removedInput schema / properties / since_iso / x-deprecated-alias-of
```
Removed value: -"since"
```

Changed4 schema fields changedSep 14, 2026

addedInput schema / properties / since

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results",
+  "title": "Since"
+}

addedInput schema / properties / since_iso / deprecated
```
Added value: +true
```

changedInput schema / properties / since_iso / description

Previous value: -"ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results."New value: +"Deprecated: use `since`, which means the same thing."

addedInput schema / properties / since_iso / x-deprecated-alias-of
```
Added value: +"since"
```

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."New value: +"Maximum results to return (1-100)."

Changed4 schema fields changedJun 7, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum messages to return (1-100)"New value: +"Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page."

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / since_iso / description

Previous value: -"ISO timestamp; only return messages created after this moment. Omit to return the most recent ``limit`` messages across all groups."New value: +"ISO 8601 timestamp; only return results created strictly after this moment. Omit (or pass ``null``) to return the most recent ``limit`` results."

AddedMay 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (read-only, idempotent, non-destructive), the description discloses exclusions ('soft-deleted messages and pending/declined-invite groups'), strict timestamp filtering, ordering, and clarifies response fields (`count`, `has_more`, deprecated `total`). This adds significant behavioral context not available in annotations.

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 efficiently structured with front-loaded purpose and use case, followed by parameter behavior and response semantics. Every sentence adds value, and the deprecated `total` clarification earns its place by preventing misuse.

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?

The description covers scope, filtering, ordering, exclusions, and response semantics. It does not explicitly explain how to paginate further (e.g., using the last timestamp as a new `since` value), but the presence of `has_more` and the documented parameters make the tool usable. An explicit pagination hint would push this to a 5.

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%, so baseline is 3. The description adds meaning by explaining the default behavior when `since` is omitted, the strict-after semantics, and the relationship between `limit` and `has_more`. However, it refers to the deprecated `since_iso` rather than the primary `since` parameter, which could cause minor confusion.

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 identifies the verb 'list' and resource 'recent group messages' with an explicit scope: 'across all groups you're an accepted member of.' It also states the global nature and ordering ('globally across groups ordered newest first'), which distinguishes it from group-specific or search tools.

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 provides a concrete use case ('catch me up since I last looked') and explains behavior with and without the `since` parameter. It does not explicitly name alternatives or exclusion conditions, but the global vs. group-specific context is implied through 'across all groups' and sibling tool names.

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

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

Need Help?