Skip to main content
Glama
icoretech

Warden MCP Server

by icoretech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Collections

keychain_list_collections
Read-only

Lists collections in your vault, with optional organization filter and text search. Retrieve a filtered set of collections to manage or reference vault items.

Instructions

List collections in the current vault, optionally filtered by organizationId. Use list_org_collections when you already know the organization and only want organization-scoped collections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum returned rows (1-500).
searchNoOptional text filter; empty means no text filter.
organizationIdNoOptional organization id filter for collections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.19
    • addedInput schema / properties / limit / description
      Added value: +"Maximum returned rows (1-500)."
    • addedInput schema / properties / organizationId / description
      Added value: +"Optional organization id filter for collections."
    • addedInput schema / properties / search / description
      Added value: +"Optional text filter; empty means no text filter."
  2. Addedv0.1.20

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds the filtering behavior based on organizationId and clarifies vault scope, which provides useful context beyond 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?

Two efficient sentences: first states purpose and optional filter, second gives sibling alternative. No 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?

Adequate for a simple list tool with optional filters. No output schema, but return format is typical for a list. Missing pagination mention, but limit parameter covers that.

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 baseline 3. Description only reiterates 'optionally filtered by organizationId' without adding extra detail beyond schema descriptions.

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?

Clear verb+resource: 'List collections in the current vault'. Differentiates from sibling 'list_org_collections' via scope mention.

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

Usage Guidelines5/5

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

Explicitly states when to use alternative (list_org_collections) and optional filtering by organizationId, giving clear context.

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

Deploy Server

Other Tools