Mnemoverse Memory

vault_list

Read-onlyIdempotent

List secrets stored in your Mnemoverse Vault by alias and purpose to see which credentials exist without revealing their values. Check if a specific token or secret is saved under your account.

Instructions

List the secrets stored in your Mnemoverse Vault — by ALIAS and purpose only; the secret VALUE is never returned or shown to you, and no tool on this server returns it. Use this to check WHICH secrets the user has stored and under what alias (e.g. the user says 'do I have a GitHub token saved?'). Only YOUR account's secrets are listed.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`secrets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.15.3Oct 18, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedv0.12.1Sep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "secrets": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "alias": {
+            "description": "The secret's alias — the reference you use, never the value.",
+            "type": "string"
+          },
+          "concepts": {
+            "description": "Concept tags.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "context": {
+            "description": "The secret's purpose/context — never the value.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "alias",
+          "context",
+          "concepts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "secrets"
+  ],
+  "type": "object"
+}

Addedv0.7.0Aug 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive safely, but the description adds non-obvious behavior: values are never returned or displayed, no tool on the server can retrieve them, and only the calling account's secrets are listed. That is meaningful disclosure beyond the structured hints.

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?

Front-loaded with the core action and result shape, and the example is compact and useful. The value-is-never-returned point is restated twice ('never returned or shown to you' and 'no tool on this server returns it'), a mild redundancy that costs a point.

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?

An output schema exists, so return formatting needs no explanation, and the description still covers the one thing an agent most needs to know: what is and isn't in the response. No gaps for a zero-parameter list operation.

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, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description appropriately avoids inventing parameter guidance that doesn't exist.

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?

States a specific verb and resource (list secrets in the Mnemoverse Vault) plus the exact scope of the result (alias and purpose only). It also distinguishes itself from every sibling by asserting that no tool on this server returns the value, so memory_read can't be confused with it.

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 a clear when-to-use rule ('Use this to check WHICH secrets the user has stored and under what alias') and a concrete trigger example ('do I have a GitHub token saved?'). It does not name an explicit alternative tool or a when-not condition, but the value-retrieval case is already ruled out.

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

Deploy Server