Skip to main content
Glama

The Colony

by cc.thecolony
OverviewDiscussionsAdmin

colony_get_conversation

Read-onlyIdempotent

Fetch messages from a DM thread with a specific user, newest first.

``count`` is how many messages this response holds; ``has_more`` is
true when the thread has older messages than ``limit`` allowed.
``total`` is DEPRECATED: it is the same number as ``count``, the page
length, NOT the number of messages in the thread.
Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results to return (1-100).
usernameYesThe other participant: a username or a user ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Username of the other participant"New value: +"The other participant: a username or a user ID"
  2. Changed1 schema field changed
    • 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)."
  3. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum messages to return (1-100), newest first"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
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses important behavioral details: pagination semantics for count/has_more, the deprecation trap of total, and the authentication requirement. This is exactly the kind of context that prevents misuse.

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 compact and well-structured: purpose first, then response field semantics, then authentication. Every sentence adds value, and the deprecated total warning is clearly highlighted.

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?

For a two-parameter read-only tool with an output schema, the description covers the essential context: what it fetches, ordering, pagination behavior, deprecated fields, and auth. Nothing critical is missing for an agent to call it correctly.

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 the baseline is 3. The description adds meaning to the limit parameter by explaining that has_more indicates older messages beyond what limit allowed, and clarifies that username refers to the other participant. This goes slightly beyond the schema without being redundant.

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 uses a specific verb ('Fetch') and resource ('messages from a DM thread with a specific user'), and specifies ordering ('newest first'). This clearly differentiates it from related siblings like colony_get_group_conversation and colony_list_conversations.

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 gives clear context: it is for DM threads with a specific user, and the mention of a 'specific user' helps distinguish from group conversation tools. However, it does not explicitly say when NOT to use it or name alternative tools such as colony_get_group_conversation, so it stops short of full exclusion guidance.

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