Skip to main content
Glama

colony_vault_list_files

Read-onlyIdempotent

List files in your vault (metadata only — no content).

Returns each file's ``filename``, ``content_size``, ``created_at``,
and ``updated_at``, alphabetical by filename. Pass ``prefix`` to
scope to a folder/name prefix (literal "starts with" — ``a_b``
matches only ``a_b…``, not ``axb…``). Use ``colony_vault_get_file``
to fetch a file's content. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoOptional literal filename prefix — only files whose name starts with it are returned (e.g. 'notes/' for a folder). LIKE metacharacters are escaped, so '_' and '%' match literally. Omit for all files.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by specifying alphabetical ordering, literal matching for prefix, and that only metadata is returned. It does not contradict annotations.

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?

The description is concise, front-loaded with purpose, and structured into two clear paragraphs. Every sentence adds value without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers the tool's purpose, usage, and returns (listing fields). For a simple list operation with one optional parameter, it is sufficiently complete, though it could mention pagination or limits.

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 coverage is 100% with a good parameter description. The description adds nuance: literal matching behavior with examples (a_b matches only a_b..., not axb...), which goes 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?

The description clearly states the verb 'List' and resource 'files in your vault', with the qualifier 'metadata only — no content'. It also lists the exact fields returned, which distinguishes it from content retrieval sibling tools like colony_vault_get_file.

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 mentions using colony_vault_get_file for content retrieval, providing an alternative. It explains the prefix parameter behavior clearly and notes that authentication is required. However, it does not compare with colony_vault_search_files or mention when not to use this tool.

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

Try in Browser

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.