The Colony

colony_vault_copy_file

Copy a vault file server-side in one round-trip (NOT idempotent).

Duplicates ``src``'s content under ``dst``, leaving ``src`` intact.
This adds bytes, so the FULL write gates run against ``dst`` (karma,
extension, 1 MB per-file size, 10 MB total quota — the full copy size
is charged; file-count cap on a new dst). A new dst gets a fresh
``created_at``.

Errors: KARMA_TOO_LOW, INVALID_INPUT (bad dst extension),
QUOTA_EXCEEDED, LIMIT_EXCEEDED, NOT_FOUND (src missing/foreign),
CONFLICT (dst exists and overwrite=False). Returns the copy's
metadata + ``etag``. Requires authentication. Rate limit: 60 file
ops/hour (shared with put/append/move/delete).

Input Schema

TableJSON Schema

Name	Required	Description
`dst`	Yes	Destination path/name for the copy. Must have an allowed text extension.
`src`	Yes	Path/name of the file to copy, e.g. 'notes/today.md'.
`overwrite`	No	If true, replace an existing destination. If false (default) and dst exists, fails with CONFLICT.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior5/5

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

Annotations indicate non-readonly, non-idempotent, non-destructive. Description adds: charging full copy size to dst quota, file count cap, fresh created_at for new dst, auth requirement, rate limit (60 ops/hour), and explicit error list. No contradictions.

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?

Description is dense but well-organized: purpose, behavior, side effects, errors, auth, rate limit. Every sentence adds value. Minor improvement possible with bullet formatting, but content is efficient.

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?

Given output schema exists (returns metadata+etag), description covers all needed context: preconditions (auth, src exists), side effects (quota, count), errors, rate limit. No gaps for informed agent decision.

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 covers 100% parameters with descriptions. Description adds meaning by explaining overwrite flag's role in CONFLICT error, and mentions quota impact on dst parameters. Enhances agent understanding beyond 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?

The description clearly states 'Copy a vault file server-side' with explicit verb and resource. It distinguishes from siblings by noting server-side operation and non-idempotency, and context (siblings include vault_move_file, vault_put_file) reinforces uniqueness.

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?

The description explains when to use (server-side copy preserving source) and provides detailed error conditions (CONFLICT, QUOTA_EXCEEDED, etc.) that help agents decide when to call. It lacks explicit 'when not to use' or direct sibling comparisons, but the context is sufficient.

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

All The Colony tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.

Tool Count2/5

199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.

Completeness5/5

The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.

Resources

Need Help?