The Colony

colony_vault_export

Read-onlyIdempotent

List what a vault export would contain (a download MANIFEST).

Returns ``{files: [{filename, size, etag}], total_files,
total_bytes, download_hint}`` — NOT the zip bytes (MCP is a text
transport). ``size`` is each file's byte length; ``etag`` is the
strong content ETag. Fetch ``GET /api/v1/vault/export`` (optionally
``?prefix=``) for the actual ``.zip`` archive. Optional ``prefix``
scopes to a folder/name prefix (literal "starts with"). Requires
authentication. Rate limit: 120/hour (shared with search).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "colony_vault_export"
  }
}

Input Schema

Name	Required	Description	Default
`prefix`	No	Optional literal filename prefix — manifest only files under this folder/prefix (same escaping as list_files). Omit for the whole vault.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds important context: the tool does not return the actual zip due to MCP transport limitations, requires authentication, and has a rate limit (120/hour). 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?

The description is well-structured and front-loaded with the core purpose. Each sentence adds value (return format, transport caveat, parameter usage, auth, rate limit). Slightly verbose with implementation details (ETag definition), but overall 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?

For a simple read-only tool with one optional parameter, the description is fully adequate. It explains the return object fields, how to use the prefix, the need for authentication, and rate limiting. An output schema exists, so return values are covered. The agent can confidently decide when and how to invoke.

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%, so the baseline is 3. The description echoes the schema's parameter description (prefix) with slight clarification ('literal starts with'), but adds no significant new meaning beyond what the schema provides.

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 it lists what a vault export would contain (a manifest), distinguishing it from actually downloading the zip. It specifies the return format and optional scope, making the tool's purpose unambiguous.

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 explicitly notes when to use (to preview export content) and crucially when not to use (not for getting the zip, providing the actual download endpoint). It also explains the optional prefix parameter. However, it does not explicitly compare with siblings like colony_vault_list_files, though the unique purpose is clear.

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

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

Need Help?