Mnemoverse Memory

vault_list

Read-onlyIdempotent

List stored secret aliases and purposes from your Mnemoverse Vault, never exposing secret values. Use it to check which secrets you have saved, such as a GitHub token.

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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`secrets`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds a critical behavioral guarantee: 'the secret VALUE is never returned or shown to you, and no tool on this server returns it' and 'Only YOUR account's secrets are listed'. These privacy and scoping constraints are not derivable from annotations and are essential for correct use, making this a strong behavioral disclosure.

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 front-loaded with the core purpose, immediately followed by the most critical constraint (value never returned), then a practical use case and account scoping. Every sentence serves a distinct purpose; even the seemingly repetitive privacy clauses add nuance (not returned, not shown, not available from any tool). It is efficient and highly informative.

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?

Given the tool has no parameters, an output schema exists, and the annotations cover safety properties, the description provides everything an agent needs: what the tool lists, privacy guarantees, and account scope. There is no missing information that would affect correct invocation.

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 schema fully covers parameter semantics (100% coverage trivially). The baseline for 0 parameters is 4; the description adds no parameter-specific info, but none is needed, so a 4 is appropriate.

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 tool 'List the secrets stored in your Mnemoverse Vault' with a specific verb and resource, and specifies the output is limited to 'ALIAS and purpose only'. It differentiates from the sibling memory_* tools by explicitly scoping to the vault and secrecy domain, so an agent can instantly recognize its function.

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 gives an explicit when-to-use case: 'Use this to check WHICH secrets the user has stored and under what alias' with a concrete example. It does not mention when not to use or alternative tools, but since the sibling tools are all in a different domain, the guidance is sufficient for the context.

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

Deploy Server