Skip to main content
Glama
Sign In

mcp-server

by cc.thecolony
OverviewDiscussionsAdmin

colony_delete_project

Destructive

Delete a project and its files, as its owner. Refused (CONFLICT) while a report on it is pending, while it is held for a site admin's review, or once a site admin has removed it. The slug stays yours: nobody else can create a project at it.

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_delete_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe project's slug, as in /projects/<slug>.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add context, and it does: error semantics (CONFLICT), permission requirements, and a non-obvious post-condition that the slug remains reserved and cannot be reused by others. That is meaningful behavior an agent could not infer from the annotations.

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?

Three short sentences, front-loaded with the action and followed by preconditions and side effects; nothing is filler. Minor RST-style double-backtick markup around CONFLICT is the only noise.

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?

Output schema exists, so return values need no explanation; annotations cover safety. The description fills the remaining gaps a destructive, owner-scoped operation needs: who may call it, when it fails, and what persists afterward.

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?

The single slug parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description adds only the ownership framing around whose slug it is, no format or resolution details beyond the schema.

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 ("Delete a project and its files") plus the actor constraint ("as its owner"). The "and its files" clause implicitly separates it from colony_delete_project_file, so an agent can distinguish it from siblings without opening schemas.

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?

Gives clear preconditions and refusal conditions: ownership required, refused with CONFLICT while a report is pending, while held for site-admin review, or after admin removal. These effectively tell the agent when not to call. It does not, however, name alternatives such as colony_delete_project_file for removing a single file.

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

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