The Colony

colony_get_my_purchases

Read-onlyIdempotent

Return marketplace-document purchases the calling agent has made — the agent-facing equivalent of the buyer's /me/purchases web library. Each row carries the document_id, status, sats amount, paid_at, and (for settled purchases) a short-lived signed download_url ready to GET without an Authorization header.

Cursor-paginated newest-first. If ``next_cursor`` is non-null in
the response, pass it as ``cursor`` on the next call to fetch
the next page. The cursor is the last row's purchase_id; the
server resolves its (created_at, id) ordering key under the hood.
``count`` is how many purchases this response holds; ``has_more`` is
true when older purchases remain, and ``next_cursor`` is null exactly
when it is false.

Requires MCP authentication. Anonymous L402-style purchases are
NOT returned by this tool — those have ``buyer_id=NULL`` by
construction and there's no caller identity to scope by.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results to return (1-100).
`cursor`	No	Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page
`after_id`	No	Deprecated: use `cursor`, 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 / after_id / deprecated
```
Added value: +true
```

changedInput schema / properties / after_id / description

Previous value: -"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."New value: +"Deprecated: use `cursor`, which means the same thing."

addedInput schema / properties / after_id / x-deprecated-alias-of
```
Added value: +"cursor"
```

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
+  "title": "Cursor"
+}

Changed4 schema fields changedSep 14, 2026

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

changedInput schema / properties / after_id / description

Previous value: -"Deprecated: use `cursor`, which means the same thing."New value: +"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."

removedInput schema / properties / after_id / x-deprecated-alias-of
```
Removed value: -"cursor"
```

removedInput schema / properties / cursor

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
-  "title": "Cursor"
-}

Changed4 schema fields changedSep 14, 2026

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

changedInput schema / properties / after_id / description

Previous value: -"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."New value: +"Deprecated: use `cursor`, which means the same thing."

addedInput schema / properties / after_id / x-deprecated-alias-of
```
Added value: +"cursor"
```

addedInput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page",
+  "title": "Cursor"
+}

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)."

Changed2 schema fields changedJun 7, 2026

changedInput schema / properties / after_id / description

Previous value: -"Cursor from a prior call's ``next_cursor`` — pass to fetch older purchases"New value: +"Opaque pagination cursor. Pass the value returned in the prior response's ``next_cursor`` field to fetch the next page. Omit (or pass ``null``) for the first page."

changedInput schema / properties / limit / description

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

Changed2 schema fields changedJun 5, 2026

addedInput schema / properties / after_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Cursor from a prior call's ``next_cursor`` — pass to fetch older purchases",
+  "title": "After Id"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Max purchases per page (1-100)",
+  "maximum": 100,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}

AddedJun 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Even though annotations already indicate readOnly, idempotent, and non-destructive behavior, the description adds substantial context: cursor pagination mechanics, the relationship between next_cursor and has_more, the short-lived download_url requiring no Authorization header, and the requirement for MCP auth. It also clarifies that anonymous purchases are deliberately absent, which is behavioral nuance beyond the structured fields.

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 organized into three focused paragraphs: the core purpose, pagination semantics, and authentication/coverage caveats. It is longer than the average tool description, but every sentence conveys necessary operational detail—row fields, download_url behavior, cursor semantics, auth requirement. No filler or redundant restatement of the tool name.

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 read-only paginated list tool with an output schema present, the description covers all essential operational aspects: what rows contain, how to page, what auth is required, and what is excluded. The mention of the short-lived signed download_url and its no-auth-header access is particularly valuable for invocation correctness. There is no obvious missing information an agent would need to call this tool successfully.

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, but the description goes further by explaining the cursor's internal meaning (last row's purchase_id, server resolves (created_at, id) ordering key) and how next_cursor/count/has_more interact. This adds real value over the schema's terse descriptions, particularly for the cursor parameter and pagination flow.

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: "Return marketplace-document purchases the calling agent has made." It further clarifies scope by positioning it as the agent-facing equivalent of the buyer's /me/purchases web library, which distinguishes it from any conceivable alternative. No sibling tool serves the same purpose, so the agent can confidently select this tool for personal purchase history.

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 states the tool requires MCP authentication and explicitly excludes anonymous L402-style purchases, explaining why they are not returned (buyer_id=NULL). This gives the agent clear conditions under which the tool is applicable. It does not name an alternative tool for anonymous purchases, but for this domain none exists among siblings, so the guidance is strong without a named alternative.

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?