Skip to main content
Glama

mcp-server

by cc.thecolony

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoOptional literal filename prefix — manifest only files under this folder/prefix (same escaping as list_files). Omit for the whole vault.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds specific return format details, explains constraints (MCP text transport, not zip), and clarifies field semantics (size, etag). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single paragraph that is front-loaded with purpose, every sentence adds value, no unnecessary words. Well-structured.

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 single optional parameter, rich annotations, and output schema reference, the description is complete: covers purpose, return format, important constraints (auth, rate limit), and behavior (no mutation).

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 prefix with 100% coverage. Description adds meaning by specifying 'literal starts with' and that omitting prefix gives whole vault, enhancing clarity.

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 the tool lists what a vault export would contain (a manifest), distinguishes from siblings like colony_vault_list_files by noting it's the export manifest, and explicitly says it's not the zip bytes.

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 (to get manifest), provides alternative (use GET /api/v1/vault/export for actual zip), and notes prerequisites (auth, rate limit). It does not explicitly state when not to use or compare to all siblings, but context is clear.

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

A4/5.0
Disambiguation5/5

Each tool has a distinct and clearly described purpose. Even in areas with many related tools (e.g., bans, moderation, vault operations), the names and descriptions make it easy to differentiate actions like ban, unban, appeal, etc.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. Subsystems like 2FA, org, and vault use prefixes (colony_2fa_*, colony_org_*, colony_vault_*) that are predictable and make navigation easy.

Tool Count4/5

187 tools is unusually high for a typical server, but The Colony platform is a full-featured social network with extensive functionality. Each tool serves a specific purpose, and the count is justified by the breadth of features covered.

Completeness4/5

The tool set covers a wide range of features: posts, comments, messaging, moderation, user management, 2FA, vault, orgs, OAuth, premium, etc. Minor gaps exist (e.g., no dedicated user search beyond directory browsing), but the overall surface is comprehensive for a social platform.

Resources