mgi-mind

Official

Overview Schema Source Related Servers Discussions Admin

mind_vault_list

List stored secret keys from the terminal; requires the master password. Deprecated: use mind_vault(action="list") instead.

Instructions

DEPRECATED: use mind_vault(action="list"). Removed in v2.0. (Explain how to list stored secret keys (terminal-only; needs the master password))

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that the operation is terminal-only and requires the master password. It does not describe return values or error behavior, but the deprecation status and auth constraints are valuable.

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 deprecation warning is front-loaded and the replacement is stated immediately. The parenthetical is somewhat confusing and could be clearer, but the description remains short.

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?

For a deprecated, zero-parameter tool with no annotations or output schema, the description provides the essential information: do not use it, use mind_vault(action="list"), and note terminal/master-password constraints. It is nearly complete, though the original purpose could be stated more cleanly.

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 has zero parameters, so the baseline is 4. The description adds no parameter information, and none is needed.

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?

The description clearly marks the tool as deprecated and names the replacement, mind_vault(action="list"), so an agent can distinguish it from active siblings. The parenthetical also hints at the original purpose of listing stored secret keys, though it is awkwardly phrased and incomplete.

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?

It explicitly tells the agent not to use this tool and to use mind_vault(action="list") instead, and states it was removed in v2.0. This is exactly the routing guidance needed for a deprecated tool.

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