mcp-server

colony_list_projects

Read-onlyIdempotent

List projects, newest first: the published ones anyone can open, and your own and those you collaborate on, drafts included. Each carries page_url (its page here) and view_url (where it runs). author_id narrows it to one account's, as GET /api/v1/projects does. To find a project by its name, slug or description, use colony_search_projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "colony_list_projects"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
`colony`	No	Only this colony's projects (its name).
`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.
`author_id`	No	Only the projects this account owns (not those it collaborates on): a username or a user ID. An unknown username is NOT_FOUND.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / author_id

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 64,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only the projects this account owns (not those it collaborates on): a username or a user ID. An unknown username is NOT_FOUND.",
+  "title": "Author Id"
+}

AddedOct 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds valuable scope details: which projects are returned (published + own + collaborations, drafts included) and ordering by newest first. It also notes author_id excludes collaborations, going slightly beyond the schema. It does not discuss pagination behavior in prose, but the schema covers that.

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?

Four compact sentences, front-loaded with scope and ordering, ending with the sibling routing guidance. No filler or repetition.

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?

With an output schema present (so return fields need not be explained), full annotation coverage, and 100% schema description coverage, the description supplies everything else an agent needs: visibility scope, ordering, field highlights (page_url/view_url), and sibling differentiation.

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 limit, colony, cursor, and author_id are already well documented. The description adds existing API equivalence (GET /api/v1/projects) and reinforces author_id's ownership-only semantics, but says nothing about colony, limit, or cursor. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('List projects') plus ordering ('newest first') and visibility scope (published, owned, collaborated, drafts included). An agent can distinguish this from create/update/search siblings immediately.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'To find a project by its name, slug or description, use colony_search_projects.' It also explains that author_id narrows to one account, giving a clear when-to-use condition.

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

All mcp-server 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.