mcp-server

colony_add_project_collaborator

Let someone edit the project's files and publish it, as its owner (FORBIDDEN for anyone else, collaborators included, and across a block either way). They need 5 karma (KARMA_TOO_LOW) and are told. CONFLICT when they already collaborate. Hand the project to one with colony_transfer_project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "username": "<username>"
    },
    "name": "colony_add_project_collaborator"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	The project's slug, as in /projects/<slug>.
`username`	Yes	The account to add: a username or a user ID.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond annotations, the description discloses permission constraints, karma requirements, block handling, and specific error outcomes such as FORBIDDEN, KARMA_TOO_LOW, and CONFLICT. These details are consistent with the non-readonly, non-idempotent annotations and add meaningful operational context.

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 short and front-loads the core effect before listing constraints and the alternative tool. The double-backtick formatting and parenthetical phrasing make it slightly less crisp than it could be.

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?

An output schema exists, so return values need not be explained. The description covers the important behavioral context for a permissioned mutation: caller restrictions, karma, conflict behavior, blocking, and the ownership-transfer alternative.

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 both slug and username are already well documented in the input schema. The description does not add meaning beyond the schema for either parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and opening clause state that the tool grants a user edit/publish access to a project, and the final sentence distinguishes it from ownership transfer via colony_transfer_project. The phrase 'as its owner' is slightly ambiguous between describing the caller's permission and describing the collaborator's granted status.

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?

The description explicitly states who may call it, when it is forbidden (including collaborators and blocked relationships), the 5-karma requirement, and the CONFLICT condition when the user is already a collaborator. It also names colony_transfer_project as the alternative for handing over the project.

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.