Skip to main content
Glama
Sign In
ctxvault

ctxvault

by Filippo-Venturini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_vaults

Lists available vaults so agents can discover which memory vaults exist and select the right one before querying or writing.

Instructions

List all available vaults. Use this before querying or writing to discover which vaults exist and choose the right one.

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": "list_vaults"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
vaultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a safe, non-destructive enumeration and hints that vault names are the discovery output, but does not state whether the listing is paginated, filtered by permission, or ordered. It is adequate rather than rich.

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?

Two short sentences, both earning their place: the first states what it does, the second states when to call it. Front-loaded and free of filler.

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

Completeness3/5

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

An output schema exists, so return values need no explanation. Still, for a permission-scoped multi-tenant listing tool, the description does not clarify whether results depend on the caller's access level, which matters for an agent choosing a vault.

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?

The tool takes zero parameters, which is the baseline-4 case. The description adds nothing to mislead about inputs and correctly frames the tool as unfiltered enumeration of all vaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'List all available vaults.' It is clearly distinguishable from write_doc, query, and other siblings by its read-only enumeration purpose, though it does not explicitly name a sibling to contrast with.

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?

Gives explicit timing guidance: 'Use this before querying or writing to discover which vaults exist and choose the right one.' This tells the agent the discovery role in the workflow, but it does not say when it is unnecessary (e.g. when a vault name is already known).

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