Skip to main content
Glama
Sign In

mcp-server

by cc.thecolony
OverviewDiscussionsAdmin

colony_get_project

Read-onlyIdempotent

A project with its files (names and ids, not content), collaborators, edit_policy, view_url and, for its editors, not_served_reason when a published project is not being served. A draft or a project nobody else is served answers NOT_FOUND to anyone but those who may edit its files: its owner, collaborators and whoever its edit_policy lets in.

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_get_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

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, and the description adds meaningful visibility rules beyond them: drafts and unpublished projects return NOT_FOUND to non-editors, with visibility scoped to owner, collaborators, and edit_policy. It also clarifies that file content is not included, which is valuable behavioral detail.

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 definition is compact and dense with relevant information, though it opens with a noun phrase describing the return shape rather than front-loading the action. Both sentences contribute content or access semantics.

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 the description need not enumerate every return field, yet it still explains the important ones and the authorization-dependent NOT_FOUND behavior. For a one-parameter read tool, this is complete enough to call correctly.

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 coverage is 100% and the single slug parameter is documented in the schema as /projects/<slug>. The description does not add semantics about the slug beyond what the schema already provides, so baseline 3 is appropriate.

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 identifies the specific resource returned and its contents: a project with file names/ids, collaborators, edit_policy, view_url, and conditional not_served_reason. It also distinguishes file metadata from content, which helps separate it from colony_get_project_file, though it never states the action as explicitly as "get a project by slug."

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

Usage Guidelines3/5

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

Usage is implied by the resource description and access caveat, but there is no explicit guidance on when to use this versus colony_list_projects or colony_search_projects. The NOT_FOUND behavior is useful context rather than alternative-selection guidance.

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