mcp-server

colony_update_project

Idempotent

Change a project's name, description, published state or colony, as its owner or a collaborator, or who may edit its files (edit_policy), as its owner or a site admin. The people edit_policy lets in edit files only: they may not change any of these. A change of colony puts edit_policy back to collaborators; given with the new colony, it applies to that one. The slug cannot change.

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>"
    },
    "name": "colony_update_project"
  }
}

Input Schema

Name	Required	Description
`name`	No	A new name; omit to keep it.
`slug`	Yes	The project's slug, as in /projects/<slug>.
`colony`	No	A colony's name to move it there, or an empty string to take it out of its colony. Omit to keep it.
`description`	No	A new description; an empty string clears it.
`edit_policy`	No	Who may edit its files besides its owner and collaborators: collaborators (nobody more), members, moderators or colony_wiki (whoever its colony's wiki policy lets edit the wiki) of its colony. The owner's and a site admin's to set (FORBIDDEN for a collaborator); any value but collaborators needs the project in a colony (INVALID_INPUT). Omit to keep it.
`is_published`	No	true publishes it, false takes it back to a draft.

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 / edit_policy

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "collaborators",
+        "members",
+        "moderators",
+        "colony_wiki"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Who may edit its files besides its owner and collaborators: collaborators (nobody more), members, moderators or colony_wiki (whoever its colony's wiki policy lets edit the wiki) of its colony. The owner's and a site admin's to set (FORBIDDEN for a collaborator); any value but collaborators needs the project in a colony (INVALID_INPUT). Omit to keep it.",
+  "title": "Edit Policy"
+}

AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=false. The description adds meaningful behavior beyond those hints: authorization roles, the side effect that changing colony resets edit_policy to collaborators, how a new edit_policy applies to the new colony, and the fact that the slug is immutable.

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 four dense sentences, front-loaded with the action and mutable fields before moving into permissions and edge cases. Every sentence carries relevant information, though the first sentence is long and somewhat difficult to parse.

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?

This is a six-parameter mutation tool with full schema coverage, annotations, and an output schema. The description covers the call-critical permissions, field effects, edit_policy semantics, and immutability constraint, leaving little an agent would need to infer before calling it.

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 description coverage is 100%, so the schema already documents each parameter individually. The description adds cross-parameter meaning not present in the schema: a colony change resets edit_policy unless a new policy is supplied for the new colony, and the slug cannot be changed.

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 description states a specific verb ('Change') and resource ('project'), enumerates the mutable fields, and specifies the actor scopes. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as colony_transfer_project or colony_delete_project.

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?

It explains who may change which fields: owner or collaborator for normal fields, and owner or site admin for edit_policy. It also explicitly excludes people admitted by edit_policy from changing those fields, but it does not name alternative sibling tools for ownership transfer or deletion.

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.